Transaction | Address | Amount |
---|---|---|
0x756f...9fd86b
|
0xd16b...807dd6
|
-
674.35233 DAI
|
0x756f...9fd86b
|
0x82e6...2312ee
|
+
674.35233 DAI
|
0x756f...9fd86b
|
0x0000...000000
|
-
674.418389371956980952 aPolDAI
|
0x756f...9fd86b
|
0xd16b...807dd6
|
+
674.418389371956980952 aPolDAI
|
0x5ae8...337631
|
0x56b1...8f8096
|
-
2 GENO
|
0x5ae8...337631
|
0xdf64...ce3823
|
+
2 GENO
|
0x151f...3a5f3d
|
0x8300...b9baf4
|
-
50 DAI
|
0x151f...3a5f3d
|
0xf449...926e35
|
+
50 DAI
|
0xacda...c274ad
|
0x88b0...72b011
|
-
0.013591 DAI
|
0xacda...c274ad
|
0x4490...212ef1
|
+
0.013591 DAI
|
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.