← previous blocknext block →recent activity
Analyzing
Block #85,105,374
16 transactions · 12 stateful · 2026-07-02 11:43:29 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,105,374 · 16 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
4w05w16w2
- 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
0xe2722625…2c2b
0x065c9d…c394
3 touches
1 conflict
0x15b249e6…11d5
0x065c9d…c394
2 touches
0 conflicts
0x657af660…48f0
0x065c9d…c394
2 touches
0 conflicts
0x6d4a163c…48d7
0x065c9d…c394
2 touches
0 conflicts
0x7c636e3f…1ae9
0x065c9d…c394
2 touches
0 conflicts
0xb4df60b7…dfdd
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