← previous blocknext block →recent activity
Analyzing
Block #85,374,070
11 transactions · 9 stateful · 2026-07-03 17:34:00 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,374,070 · 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
1w05w06w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d8cb133…0ff7
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2a149d95…3140
0x065c9d…c394
3 touches
1 conflict
0x559a6f74…56c4
0x065c9d…c394
3 touches
1 conflict
0x00000000…00ca
0x4771aa…a2ac
2 touches
0 conflicts
0xbf34c774…1214
0x4771aa…a2ac
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 0x5d8cb13359…1c0ff7
Audit this contract →
← previous block·next block →recent activity