← previous blocknext block →recent activity
Analyzing
Block #85,574,431
23 transactions · 17 stateful · 2026-07-04 15:48:00 UTC
Parallelism
91/100
Blocked
12%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,574,431 · 23 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
1w04w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x0232d7fb…e0d9
0x40c49f…2af0
4 touches
1 conflict
0x45550d84…bc01
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x581f6cfb…49a4
0x065c9d…c394
2 touches
0 conflicts
0x5e020386…f3d4
0x065c9d…c394
2 touches
0 conflicts
0x887b56a7…e7c6
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity