← previous blocknext block →recent activity
Analyzing
Block #96,259,944
9 transactions · 7 stateful · 2026-08-15 17:12:14 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,259,944 · 9 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
1w02w03w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefeb7937…c283
0x34b655…2a6f
4 touches
1 conflict
0xb3826464…b02d
0x34b655…2a6f
4 touches
1 conflict
0xc0b9bd73…7f1c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xca86fe92…6b3b
0x34b655…2a6f
4 touches
1 conflict
0xcc3678e9…76f7
0x34b655…2a6f
4 touches
1 conflict
0xdeaa385f…6b8b
0x34b655…2a6f
4 touches
1 conflict
0xe7bd356d…d23a
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 0xefeb793761…25c283
Audit this contract →
← previous block·next block →recent activity