← previous blocknext block →recent activity
Analyzing
Block #86,811,932
24 transactions · 22 stateful · 2026-07-10 09:30:24 UTC
Parallelism
71/100
Blocked
55%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,811,932 · 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
1w03w16w07w18w29w310w413w316w418w219w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x8d888c90…5479
0x34b655…2a6f
10 touches
10 conflicts
0x565f28e7…6746
0x34b655…2a6f
8 touches
6 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
8 touches
6 conflicts
0xa6d52fb7…c165
0x34b655…2a6f
8 touches
6 conflicts
0x657f5161…af39
0x34b655…2a6f
6 touches
3 conflicts
0xa2ec331b…6100
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