← previous blocknext block →recent activity
Analyzing
Block #86,700,340
14 transactions · 12 stateful · 2026-07-09 21:05:01 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,700,340 · 14 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
2w04w05w17w28w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x64ac7daf…c064
0x34b655…2a6f
6 touches
3 conflicts
0xb46bb9bf…deb7
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa7013be2…c0a8
0x34b655…2a6f
4 touches
1 conflict
0x1bbc01d7…0bcb
0x34b655…2a6f
4 touches
1 conflict
0xe28e89d1…0cf0
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity