← previous blocknext block →recent activity
Analyzing
Block #86,220,676
23 transactions · 22 stateful · 2026-07-07 15:37:45 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,220,676 · 23 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
1w02w13w24w16w015w216w320w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5ddae5c0…8b46
0xd32edf…ff58
5 touches
3 conflicts
0x839c0c71…bada
0x34b655…2a6f
4 touches
1 conflict
0x98a1bad6…5130
0x34b655…2a6f
4 touches
1 conflict
0xa2e4453b…a207
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity