← previous blocknext block →recent activity
Analyzing
Block #85,145,393
18 transactions · 17 stateful · 2026-07-02 16:10:53 UTC
Parallelism
72/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,145,393 · 18 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
1w05w16w28w09w010w112w113w314w416w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x975abaa6…0e7c
0x065c9d…c394
8 touches
6 conflicts
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0xef10b3e3…a0d7
0x065c9d…c394
5 touches
3 conflicts
0x347327ff…3863
0x34b655…2a6f
4 touches
1 conflict
0x4caf91f9…8ab5
0x34b655…2a6f
4 touches
1 conflict
0x4d55de89…1c91
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity