← previous blocknext block →recent activity
Analyzing
Block #99,989,625
19 transactions · 18 stateful · 2026-08-28 20:08:09 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.68
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,989,625 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w18w29w110w312w216w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95e19af7…84d6
0x34b655…2a6f
8 touches
6 conflicts
0xb46bb9bf…deb7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x97420b44…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xd6980aa4…a052
0x34b655…2a6f
4 touches
1 conflict
0xba1edffb…323e
0x34b655…2a6f
4 touches
1 conflict
0xfc81faf7…1417
0x34b655…2a6f
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0x95e19af7ab…ab84d6
Audit this contract →
← previous block·next block →recent activity