← previous blocknext block →recent activity
Analyzing
Block #86,904,361
14 transactions · 13 stateful · 2026-07-10 19:48:34 UTC
Parallelism
64/100
Blocked
31%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,904,361 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d64d7f8…ce93
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa3a98237…7b46
0x34b655…2a6f
4 touches
1 conflict
0xa8b12145…7275
0x34b655…2a6f
4 touches
1 conflict
0xa8b12145…7276
0x34b655…2a6f
4 touches
1 conflict
0xadbc79c0…9c86
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 0x9d64d7f8fe…8bce93
Audit this contract →
← previous block·next block →recent activity