← previous blocknext block →recent activity
Analyzing
Block #86,249,314
53 transactions · 42 stateful · 2026-07-07 18:49:04 UTC
Parallelism
85/100
Blocked
55%
Avg conflicts / tx
1.08
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,249,314 · 53 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w19w210w315w218w320w422w523w640w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xbf7e6bf8…2b70
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x17c44db3…8888
0xa6afd3…d132
8 touches
6 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
8 touches
6 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity