← previous blocknext block →recent activity
Analyzing
Block #85,972,351
26 transactions · 21 stateful · 2026-07-06 11:59:45 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,972,351 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w011w012w117w120w221w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x54ae7762…e272
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0001
0x04ddf6…7f33
4 touches
1 conflict
0x00000000…0003
0x04ddf6…7f33
4 touches
1 conflict
0x7054790d…6034
0x065c9d…c394
4 touches
1 conflict
0xa4f80979…4d71
0x065c9d…c394
4 touches
1 conflict
0xd35bb5ac…3586
0x065c9d…c394
4 touches
1 conflict
0xaeabffea…5dd4
0x0a3323…0a3c
4 touches
1 conflict
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