← previous blocknext block →recent activity
Analyzing
Block #86,635,036
24 transactions · 21 stateful · 2026-07-09 13:47:47 UTC
Parallelism
92/100
Blocked
14%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,635,036 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w08w117w021w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d7ff6bb…f729
0x34b655…2a6f
4 touches
1 conflict
0xa29182a1…c12c
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc6fa5268…6ae0
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xd58cc679…0f62
0x40c49f…2af0
2 touches
0 conflicts
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
1 conflict on slot 0x7d7ff6bb1e…8bf729
Audit this contract →
← previous block·next block →recent activity