← previous blocknext block →recent activity
Analyzing
Block #86,564,170
13 transactions · 12 stateful · 2026-07-09 05:53:07 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,564,170 · 13 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
2w06w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79d50d4a…951d
0x34b655…2a6f
4 touches
1 conflict
0xe2e56921…8e8d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x5d7f309d…5145
0x34b655…2a6f
2 touches
0 conflicts
0x751349fe…0be8
0x34b655…2a6f
2 touches
0 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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 0x79d50d4ae7…7e951d
Audit this contract →
← previous block·next block →recent activity