← previous blocknext block →recent activity
Analyzing
Block #85,573,473
11 transactions · 5 stateful · 2026-07-04 15:41:38 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,573,473 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdaa7c05d…4cce
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7d22ccdc…5ac4
0x065c9d…c394
3 touches
1 conflict
0x12e4d580…c196
0x065c9d…c394
2 touches
0 conflicts
0x46333ede…fb36
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x57c0658f…72bf
0x065c9d…c394
2 touches
0 conflicts
0x75e33c7b…34b0
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
1 conflict on slot 0xdaa7c05d48…114cce
Audit this contract →
← previous block·next block →recent activity