Transaction | Address | Amount |
---|---|---|
0x20d1...a1fd3c
|
0xac31...072d91
|
-
1.55346523095918327 MATIC
|
0x20d1...a1fd3c
|
0x5184...47f764
|
+
1.55346523095918327 MATIC
|
0x20d1...a1fd3c
|
0xac31...072d91
|
-
8.597554430671026682 MATIC
|
0x20d1...a1fd3c
|
0x598a...96674a
|
+
8.597554430671026682 MATIC
|
0xd0f8...02cee8
|
0x0c1e...60d36f
|
-
0.013713132117427333 MATIC
|
0xd0f8...02cee8
|
0x3c22...53cf62
|
+
0.013713132117427333 MATIC
|
0xd0f8...02cee8
|
0x3c22...53cf62
|
-
0.013713132117427333 MATIC
|
0xd0f8...02cee8
|
0x4d73...a178e2
|
+
0.013713132117427333 MATIC
|
0xd0f8...02cee8
|
0x4d73...a178e2
|
-
0.001246648374311575 MATIC
|
0xd0f8...02cee8
|
0x0dca...2e2381
|
+
0.001246648374311575 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.