Transaction | Address | Amount |
---|---|---|
0xf5b1...945dc6
|
0x3c22...53cf62
|
-
1.004832611875365266 MATIC
|
0xf5b1...945dc6
|
0x4d73...a178e2
|
+
1.004832611875365266 MATIC
|
0xc010...600021
|
0x0d50...df1270
|
-
10.273465867655246252 MATIC
|
0xc010...600021
|
0x1111...960582
|
+
10.273465867655246252 MATIC
|
0xc010...600021
|
0x1111...960582
|
-
10.273465867655246252 MATIC
|
0xc010...600021
|
0xc590...74c02b
|
+
10.273465867655246252 MATIC
|
0xc010...600021
|
0xc590...74c02b
|
-
0.089892826341983405 MATIC
|
0xc010...600021
|
0x930d...064eac
|
+
0.089892826341983405 MATIC
|
0xc010...600021
|
0xc590...74c02b
|
-
10.183573041313262847 MATIC
|
0xc010...600021
|
0xbbcc...3ce8af
|
+
10.183573041313262847 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.