← previous blocknext block →recent activity
Analyzing
Block #86,984,336
24 transactions · 21 stateful · 2026-07-11 04:42:57 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
1.25
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,984,336 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w212w313w414w415w116w517w520w221w423w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xdb3937e8…23cb
0x34b655…2a6f
6 touches
3 conflicts
0xde4f189a…c6f3
0x34b655…2a6f
6 touches
3 conflicts
0x1e48811e…2e39
0x34b655…2a6f
6 touches
3 conflicts
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0x1299b030…e115
0x34b655…2a6f
6 touches
3 conflicts
0x4e3abeff…18eb
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity