Transaction | Address | Amount |
---|---|---|
0xbe9d...f42133
|
0x896d...375575
|
-
0.031080210373576876 MATIC
|
0xbe9d...f42133
|
0x21da...dee0a0
|
+
0.031080210373576876 MATIC
|
0xbe9d...f42133
|
0x21da...dee0a0
|
-
0.657030076330352512 MATIC
|
0xbe9d...f42133
|
0x7ae4...68f3b8
|
+
0.657030076330352512 MATIC
|
0xbe9d...f42133
|
0x21da...dee0a0
|
-
80.051990159834917546 MATIC
|
0xbe9d...f42133
|
0x7269...236d09
|
+
80.051990159834917546 MATIC
|
0xbe9d...f42133
|
0x21da...dee0a0
|
-
0.031080210373576876 MATIC
|
0xbe9d...f42133
|
0x7269...236d09
|
+
0.031080210373576876 MATIC
|
0xbe9d...f42133
|
0x896d...375575
|
-
0.235031721672090097 MATIC
|
0xbe9d...f42133
|
0xbd09...3ca8d2
|
+
0.235031721672090097 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.