← previous blocknext block →recent activity
Analyzing
Block #85,668,969
23 transactions · 20 stateful · 2026-07-05 02:17:27 UTC
Parallelism
78/100
Blocked
55%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,668,969 · 23 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
1w02w13w26w37w19w010w111w212w313w416w417w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0x5b1448f1…6b80
0xd32edf…ff58
9 touches
10 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
6 touches
3 conflicts
0xd53220ed…4738
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x033cf007…136d
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: 0x04fdeac2…f747d7
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity