← previous blocknext block →recent activity
Analyzing
Block #86,853,683
31 transactions · 24 stateful · 2026-07-10 14:09:38 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,853,683 · 31 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
1w05w06w17w08w29w111w112w013w118w220w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x527f20e3…82e7
0x754704…b603
6 touches
3 conflicts
0x49a97bff…33ed
0x34b655…2a6f
6 touches
3 conflicts
0xd9f1e40f…09a3
0x3bd359…433a
6 touches
3 conflicts
0xbb0d28dc…15c7
0x34b655…2a6f
6 touches
3 conflicts
0x9194f4a3…10b8
0x754704…b603
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity