← previous blocknext block →recent activity
Analyzing
Block #96,294,329
9 transactions · 8 stateful · 2026-08-15 20:05:11 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,294,329 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xc7277122…8339
0x34b655…2a6f
4 touches
1 conflict
0xe4db7c8b…29c7
0x34b655…2a6f
4 touches
1 conflict
0x5b0edc1d…65d6
0x34b655…2a6f
2 touches
0 conflicts
0x6be37e18…14e0
0x34b655…2a6f
2 touches
0 conflicts
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 0xe732567db9…26b65d
Audit this contract →
← previous block·next block →recent activity