← previous blocknext block →recent activity
Analyzing
Block #86,905,998
17 transactions · 17 stateful · 2026-07-10 19:59:33 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,905,998 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w010w111w212w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x31023c37…b82c
0xd32edf…ff58
7 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x0b277fb8…2d82
0x34b655…2a6f
4 touches
1 conflict
0x0c366266…77e1
0x34b655…2a6f
4 touches
1 conflict
0x11d3004e…e104
0x34b655…2a6f
4 touches
1 conflict
0x1c503794…b0da
0x34b655…2a6f
4 touches
1 conflict
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