← previous blocknext block →recent activity
Analyzing
Block #86,709,721
13 transactions · 12 stateful · 2026-07-09 22:07:36 UTC
Parallelism
54/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,709,721 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w28w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0xd1952ceb…56be
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x56f7a389…74fd
0x34b655…2a6f
4 touches
1 conflict
0x79287e09…898a
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180d
0x34b655…2a6f
4 touches
1 conflict
0x8212e232…180e
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity