← previous blocknext block →recent activity
Analyzing
Block #86,954,346
21 transactions · 20 stateful · 2026-07-11 01:22:33 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,954,346 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w210w011w113w214w215w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e3abeff…18eb
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x4f403319…d31b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x17c44db3…8888
0xa6afd3…d132
6 touches
3 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
6 touches
3 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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
6 conflicts on slot 0x4e3abefffa…8618eb
Audit this contract →
← previous block·next block →recent activity