| Transaction | Address | Amount |
|---|---|---|
|
0x6f33...2b85be
|
0xab45...254052
|
-
0 MATIC
·
0.00 USD
|
|
0x6f33...2b85be
|
0x1ab6...67abce
|
+
0 MATIC
·
0.00 USD
|
|
0x48da...e3f3f3
|
0xaacf...e3541b
|
-
0 MATIC
·
0.00 USD
|
|
0x48da...e3f3f3
|
0x4b90...0a883d
|
+
0 MATIC
·
0.00 USD
|
|
0xb01c...22dca0
|
0x2ac4...b8026a
|
-
0.009 MATIC
·
0.00 USD
|
|
0xb01c...22dca0
|
0x12f1...c08559
|
+
0.009 MATIC
·
0.00 USD
|
|
0xb01c...22dca0
|
0x2ac4...b8026a
|
-
0.0005 MATIC
·
0.00 USD
|
|
0xb01c...22dca0
|
0x2d7b...360474
|
+
0.0005 MATIC
·
0.00 USD
|
|
0xdd38...19b83a
|
0x5de4...e15ae3
|
-
0 MATIC
·
0.00 USD
|
|
0xdd38...19b83a
|
0xc8e6...51832f
|
+
0 MATIC
·
0.00 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.
