Transaction | Address | Amount |
---|---|---|
0x1d45...9ea432
|
0x1231...6f4eae
|
-
0.025145232867713061 MATIC
|
0x1d45...9ea432
|
0x1198...cf2259
|
+
0.025145232867713061 MATIC
|
0x1d45...9ea432
|
0x1198...cf2259
|
-
0.025145232867713061 MATIC
|
0x1d45...9ea432
|
0x95e6...dcab19
|
+
0.025145232867713061 MATIC
|
0x09b0...5ff214
|
0x0e1f...2cf76d
|
-
0.060986105702769586 MATIC
|
0x09b0...5ff214
|
0x3c22...53cf62
|
+
0.060986105702769586 MATIC
|
0x09b0...5ff214
|
0x3c22...53cf62
|
-
0.060986105702769586 MATIC
|
0x09b0...5ff214
|
0x4d73...a178e2
|
+
0.060986105702769586 MATIC
|
0xdd4f...241e57
|
0x0000...e06969
|
-
0.34184271723722535 MATIC
|
0xdd4f...241e57
|
0x3c22...53cf62
|
+
0.34184271723722535 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.