← previous blocknext block →recent activity
Analyzing
Block #85,541,332
14 transactions · 13 stateful · 2026-07-04 12:07:36 UTC
Parallelism
79/100
Blocked
15%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,541,332 · 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x76faa0f9…155f
0x065c9d…c394
4 touches
1 conflict
0xb5300765…23fb
0x065c9d…c394
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x60e1372f…f481
0x065c9d…c394
3 touches
1 conflict
0xa4a934d7…a3c0
0x065c9d…c394
3 touches
1 conflict
0x12bb3d2a…5e35
0x065c9d…c394
3 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