← previous blocknext block →recent activity
Analyzing
Block #96,481,864
10 transactions · 8 stateful · 2026-08-16 11:48:23 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,481,864 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3efde171…60bb
0x34b655…2a6f
4 touches
1 conflict
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 conflicts
0x5c5238c6…f2dc
0x34b655…2a6f
2 touches
0 conflicts
0x5ec23a95…74a4
0x34b655…2a6f
2 touches
0 conflicts
0x65a76d52…50b2
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 0xb9b4eff6b7…8cc3ef
Audit this contract →
← previous block·next block →recent activity