← previous blocknext block →recent activity
Analyzing
Block #85,193,219
12 transactions · 10 stateful · 2026-07-02 21:29:15 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,193,219 · 12 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0b0727ad…1c0f
0x065c9d…c394
2 touches
0 conflicts
0x263740ed…7c30
0x065c9d…c394
2 touches
0 conflicts
0x40aa1800…e701
0x065c9d…c394
2 touches
0 conflicts
0xc493882e…2cef
0x065c9d…c394
2 touches
0 conflicts
0xdf78c069…3640
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