← previous blocknext block →recent activity
Analyzing
Block #96,604,168
20 transactions · 19 stateful · 2026-08-16 22:03:50 UTC
Parallelism
55/100
Blocked
53%
Avg conflicts / tx
1.35
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #96,604,168 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w37w48w59w610w711w817w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
14 touches
21 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x33708be5…6990
0x34b655…2a6f
4 touches
1 conflict
0x4e697adf…0ac0
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0x770ea029…2ca6
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
21 conflicts on slot 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity