← previous blocknext block →recent activity
Analyzing
Block #96,611,267
11 transactions · 9 stateful · 2026-08-16 22:39:32 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,611,267 · 11 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
2w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
4 touches
1 conflict
0x7da4bbdc…0d30
0x34b655…2a6f
4 touches
1 conflict
0x0b16c8b6…7b05
0x34b655…2a6f
4 touches
1 conflict
0x15c6cd62…05e7
0x34b655…2a6f
2 touches
0 conflicts
0x174fbe56…acd2
0x34b655…2a6f
2 touches
0 conflicts
0x198ecc9b…e4cd
0x34b655…2a6f
2 touches
0 conflicts
0x5d9e6c20…078c
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
3 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity