Transaction | Address | Amount |
---|---|---|
0xda18...9b5161
|
0x0bde...449258
|
-
0.013503103085750619 MATIC
·
0.00 USD
|
0xda18...9b5161
|
0xa4ca...0736d6
|
+
0.013503103085750619 MATIC
·
0.00 USD
|
0x0eaa...6d36e3
|
0x4b6a...a6bd95
|
-
0.012229009297661268 MATIC
·
0.00 USD
|
0x0eaa...6d36e3
|
0x5ff1...6d2789
|
+
0.012229009297661268 MATIC
·
0.00 USD
|
0x0eaa...6d36e3
|
0x5ff1...6d2789
|
-
0.012225858567034175 MATIC
·
0.00 USD
|
0x0eaa...6d36e3
|
0x4337...9bec68
|
+
0.012225858567034175 MATIC
·
0.00 USD
|
0x9865...f34bee
|
0xa7fd...090f7c
|
-
1.8 MATIC
·
0.87 USD
|
0x9865...f34bee
|
0x0000...3eb395
|
+
1.8 MATIC
·
0.87 USD
|
0x9865...f34bee
|
0x0000...3eb395
|
-
1.8 MATIC
·
0.87 USD
|
0x9865...f34bee
|
0x15e0...da6525
|
+
1.8 MATIC
·
0.87 USD
|
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.