← previous blocknext block →recent activity
Analyzing
Block #96,212,929
14 transactions · 13 stateful · 2026-08-15 13:15:46 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,212,929 · 14 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
4w06w18w09w110w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
6 touches
3 conflicts
0x224d6800…4508
0x34b655…2a6f
6 touches
3 conflicts
0x0759c8f2…8408
0x34b655…2a6f
6 touches
3 conflicts
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0x5e71af98…bfd6
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
3 conflicts on slot 0x9fd372a13e…ada959
Audit this contract →
← previous block·next block →recent activity