← previous blocknext block →recent activity
Analyzing
Block #86,616,485
21 transactions · 18 stateful · 2026-07-09 11:43:51 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,616,485 · 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
1w02w14w05w16w27w38w49w011w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xf58f4849…c7c7
0x34b655…2a6f
8 touches
6 conflicts
0x12573732…e891
0x34b655…2a6f
6 touches
3 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
6 touches
3 conflicts
0x33eb5dfa…2338
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x6b2ba712…0214
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