← previous blocknext block →recent activity
Analyzing
Block #96,021,178
11 transactions · 11 stateful · 2026-08-14 21:11:16 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,021,178 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w18w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10f18761…8e0c
0x34b655…2a6f
6 touches
3 conflicts
0xafbbdaaf…448a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9ad82ccb…b08b
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x239faba0…555b
0x34b655…2a6f
4 touches
1 conflict
0x616a240e…0c47
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
3 conflicts on slot 0x10f187616c…2c8e0c
Audit this contract →
← previous block·next block →recent activity