← previous blocknext block →recent activity
Analyzing
Block #85,276,009
11 transactions · 10 stateful · 2026-07-03 06:40:47 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,276,009 · 11 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
1w03w05w16w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x4347b62a…ed5f
0x34b655…2a6f
4 touches
1 conflict
0x0e24b36b…6996
0x065c9d…c394
2 touches
0 conflicts
0x15c9ac33…811b
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x8140892f…9063
0x065c9d…c394
2 touches
0 conflicts
0xc9e022fb…4fbf
0x065c9d…c394
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