← previous blocknext block →recent activity
Analyzing
Block #85,161,644
9 transactions · 9 stateful · 2026-07-02 17:59:03 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,161,644 · 9 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
1w02w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b0dc8ea…dc0b
0x065c9d…c394
4 touches
1 conflict
0x4b153d73…038d
0x065c9d…c394
3 touches
1 conflict
0x2af73684…9960
0x851145…3f07
3 touches
1 conflict
0xde9ce38f…1db1
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
1 conflict on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity