← previous blocknext block →recent activity
Analyzing
Block #86,258,566
13 transactions · 11 stateful · 2026-07-07 19:50:54 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,258,566 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x33e0c89f…5f8c
0x065c9d…c394
3 touches
1 conflict
0x781b3282…2cff
0xd32edf…ff58
3 touches
1 conflict
0xca2a0dc4…3222
0x065c9d…c394
3 touches
1 conflict
0x2bc0452d…2317
0x065c9d…c394
3 touches
1 conflict
0x81c1a608…99e6
0x065c9d…c394
2 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
1 conflict on slot 0x77ed432f03…d6fa04
Audit this contract →
← previous block·next block →recent activity