← previous blocknext block →recent activity
Analyzing
Block #86,493,265
17 transactions · 16 stateful · 2026-07-08 21:58:51 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,493,265 · 17 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
1w02w13w25w36w415w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0276cd17…389a
0x34b655…2a6f
10 touches
10 conflicts
0xb138d087…4689
0x34b655…2a6f
10 touches
10 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…153c
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153b
0x34b655…2a6f
6 touches
3 conflicts
0x742faa78…f436
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0276cd17b4…d6389a
Audit this contract →
← previous block·next block →recent activity