← previous blocknext block →recent activity
Analyzing
Block #96,369,907
14 transactions · 14 stateful · 2026-08-16 02:25:18 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,369,907 · 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
2w05w16w09w210w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefc3c38…ff49
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbb3b1855…cd23
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0xc03846bb…73b3
0x34b655…2a6f
4 touches
1 conflict
0xc1daa030…1863
0x34b655…2a6f
4 touches
1 conflict
0xc1daa030…1864
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
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
1 conflict on slot 0xfefc3c3856…a2ff49
Audit this contract →
← previous block·next block →recent activity