← previous blocknext block →recent activity
Analyzing
Block #85,855,773
22 transactions · 18 stateful · 2026-07-05 23:02:51 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,855,773 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w07w29w110w011w112w313w314w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x2ffc9b41…f2b5
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0003
0x431fed…d150
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xe6f2ae57…2026
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x431fed…d150
4 touches
1 conflict
0x00000000…0002
0x431fed…d150
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