Transaction | Address | Amount |
---|---|---|
0xf086...e92846
|
0xd57d...a53a0f
|
-
0.0016113 MATIC
|
0xf086...e92846
|
0x048c...e84bbe
|
+
0.0016113 MATIC
|
0xf086...e92846
|
0xd57d...a53a0f
|
-
0 MATIC
|
0xf086...e92846
|
0x7308...76923b
|
+
0 MATIC
|
0x01db...50874c
|
0xcbc6...a619c6
|
-
0.000000003329081756 MATIC
|
0x01db...50874c
|
the-void |
+
0.000000003329081756 MATIC
|
0x01db...50874c
|
0xcbc6...a619c6
|
-
0.002651879634659332 MATIC
|
0x01db...50874c
|
0x048c...e84bbe
|
+
0.002651879634659332 MATIC
|
0x01db...50874c
|
0xcbc6...a619c6
|
-
0 MATIC
|
0x01db...50874c
|
0x51bd...73bf53
|
+
0 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.