← previous blocknext block →recent activity
Analyzing
Block #85,582,647
11 transactions · 11 stateful · 2026-07-04 16:42:45 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,582,647 · 11 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x25d86269…6e79
0x065c9d…c394
4 touches
1 conflict
0x1c7d78c5…c1b1
0x065c9d…c394
4 touches
1 conflict
0x119bf81a…4929
0x065c9d…c394
3 touches
1 conflict
0x20f65385…9311
0x065c9d…c394
3 touches
1 conflict
0xffa7d0a4…b10a
0x40c49f…2af0
2 touches
0 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity