← previous blocknext block →recent activity
Analyzing
Block #86,851,461
22 transactions · 19 stateful · 2026-07-10 13:54:46 UTC
Parallelism
64/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,851,461 · 22 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
1w02w17w08w19w210w311w412w518w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0xa37e64f8…ba05
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x78346476…4311
0x34b655…2a6f
6 touches
3 conflicts
0x838dc049…1c3e
0x34b655…2a6f
6 touches
3 conflicts
0x8de38574…ad6e
0x34b655…2a6f
6 touches
3 conflicts
0x8ef654b1…1fe6
0x34b655…2a6f
6 touches
3 conflicts
0xb35e663e…354e
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
6 conflicts on slot 0xec7fe04ad1…2d3c56
Audit this contract →
← previous block·next block →recent activity