← previous blocknext block →recent activity
Analyzing
Block #86,909,250
33 transactions · 31 stateful · 2026-07-10 20:21:18 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
2.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,909,250 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w519w520w221w322w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xc7a15219…7745
0xa6afd3…d132
10 touches
10 conflicts
0x202c03eb…cf33
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
10 touches
10 conflicts
0xbe9baf16…df37
0x34b655…2a6f
10 touches
10 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity