← previous blocknext block →recent activity
Analyzing
Block #85,184,955
10 transactions · 9 stateful · 2026-07-02 20:34:18 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,184,955 · 10 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
1w02w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xb0af9b81…2cb5
0x065c9d…c394
4 touches
1 conflict
0x6d5fd656…1e04
0x065c9d…c394
3 touches
1 conflict
0x31513e4b…1491
0x065c9d…c394
2 touches
0 conflicts
0x10a7d541…fc05
0x34b655…2a6f
2 touches
0 conflicts
0x78e5d878…80ba
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
0x34b655…2a6f
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity