← previous blocknext block →recent activity
Analyzing
Block #86,764,712
18 transactions · 15 stateful · 2026-07-10 04:15:05 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,764,712 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w29w310w411w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8912
0x34b655…2a6f
6 touches
3 conflicts
0xbbee202a…8913
0x34b655…2a6f
6 touches
3 conflicts
0xdfd1344f…43f5
0x34b655…2a6f
6 touches
3 conflicts
0x4979282b…2933
0x1b6862…e19c
6 touches
3 conflicts
0xa37e64f8…ba05
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity