← previous blocknext block →recent activity
Analyzing
Block #96,037,409
11 transactions · 10 stateful · 2026-08-14 22:32:56 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,037,409 · 11 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30e49b8b…5fe9
0x34b655…2a6f
4 touches
1 conflict
0x4ae3b148…7ed2
0x34b655…2a6f
4 touches
1 conflict
0x833f3561…bfd0
0x34b655…2a6f
4 touches
1 conflict
0xb713f190…5dea
0x34b655…2a6f
4 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x523cafcc…f0ed
0x34b655…2a6f
2 touches
0 conflicts
0x691e3505…dd2f
0x34b655…2a6f
2 touches
0 conflicts
0x745952b2…d90c
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 0x30e49b8b07…ff5fe9
Audit this contract →
← previous block·next block →recent activity