← previous blocknext block →recent activity
Analyzing
Block #86,978,013
18 transactions · 17 stateful · 2026-07-11 04:00:40 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,978,013 · 18 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
2w03w14w25w36w47w58w611w612w715w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd064a456…b881
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
8 touches
6 conflicts
0xa42e8482…b88f
0x34b655…2a6f
8 touches
6 conflicts
0xaa48195d…ffee
0x34b655…2a6f
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
10 conflicts on slot 0xd064a456fe…30b881
Audit this contract →
← previous block·next block →recent activity