← previous blocknext block →recent activity
Analyzing
Block #86,340,608
19 transactions · 18 stateful · 2026-07-08 04:58:38 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,340,608 · 19 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
1w02w03w14w26w38w111w013w414w517w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x419b2b6d…223a
0x34b655…2a6f
6 touches
3 conflicts
0xda46a376…f6a6
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0x4bfdcd51…9b58
0x34b655…2a6f
6 touches
3 conflicts
0x3181bd2d…cf15
0xa6afd3…d132
4 touches
1 conflict
0x034f1f86…4e8d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
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 0x419b2b6dc4…27223a
Audit this contract →
← previous block·next block →recent activity