← previous blocknext block →recent activity
Analyzing
Block #86,921,990
15 transactions · 13 stateful · 2026-07-10 21:46:22 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,921,990 · 15 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
1w02w03w15w26w38w111w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bd6b33e…9557
0x34b655…2a6f
6 touches
3 conflicts
0x008accc4…1da7
0x34b655…2a6f
4 touches
1 conflict
0x008accc4…1da8
0x34b655…2a6f
4 touches
1 conflict
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x3a76803c…4181
0x34b655…2a6f
4 touches
1 conflict
0x71c62efd…cecc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdc0cc33d…5c87
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 0x6bd6b33ee8…919557
Audit this contract →
← previous block·next block →recent activity