← previous blocknext block →recent activity
Analyzing
Block #85,757,227
13 transactions · 13 stateful · 2026-07-05 12:06:29 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,757,227 · 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
1w02w18w09w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0xa20a130c…5d59
0x34b655…2a6f
4 touches
1 conflict
0x020a49d5…24cf
0x065c9d…c394
2 touches
0 conflicts
0x1b344e58…5490
0x065c9d…c394
2 touches
0 conflicts
0x44190953…9a2c
0x065c9d…c394
2 touches
0 conflicts
0x733b1193…6e08
0x065c9d…c394
2 touches
0 conflicts
0xba327fdb…fbaf
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