Transaction | Address | Amount |
---|---|---|
0x0dc6...773dae
|
0x881d...fc6bb1
|
-
0 MATIC
|
0x0dc6...773dae
|
0x4490...fd2600
|
+
0 MATIC
|
0x0dc6...773dae
|
0x4490...fd2600
|
-
19.22827896 MATIC
|
0x0dc6...773dae
|
0x1bd6...b97143
|
+
19.22827896 MATIC
|
0x0dc6...773dae
|
0x4490...fd2600
|
-
0.19422504 MATIC
|
0x0dc6...773dae
|
0xce35...1e3abd
|
+
0.19422504 MATIC
|
0x8f00...e356a7
|
0x5ff1...6d2789
|
-
0.006284413978163174 MATIC
|
0x8f00...e356a7
|
0x4337...8fe978
|
+
0.006284413978163174 MATIC
|
0x0cb6...dee7bd
|
0xaee9...e1d0f1
|
-
0 MATIC
|
0x0cb6...dee7bd
|
0x53b2...05bb9d
|
+
0 MATIC
|
Polygon experiences an hour-long outage due to a consensus bug shortly after a major hard fork upgrade.
Polygonscan's outage on July 30 led to confusion, but the Polygon network remained stable as developers assured it was fully operational.
Polygon's Heimdall V2 experienced an outage causing temporary network disruptions, but the Bor layer remained operational.