← previous blocknext block →recent activity
Analyzing
Block #85,900,712
14 transactions · 10 stateful · 2026-07-06 04:02:09 UTC
Parallelism
79/100
Blocked
20%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,900,712 · 14 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
1w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x2655b09e…1f32
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0x8a25b887…c2ef
0x065c9d…c394
3 touches
1 conflict
0x73077c5e…6fb9
0x065c9d…c394
3 touches
1 conflict
0xf2c0b642…5eba
0x065c9d…c394
3 touches
1 conflict
0x9c216bae…685e
0x065c9d…c394
3 touches
1 conflict
0x06e40499…165e
0x69df8a…6292
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