← previous blocknext block →recent activity
Analyzing
Block #85,574,673
10 transactions · 8 stateful · 2026-07-04 15:49:36 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,574,673 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4c2fc670…8a21
0x065c9d…c394
4 touches
1 conflict
0x5ec3da7c…7641
0x065c9d…c394
3 touches
1 conflict
0x2e305e78…d862
0x065c9d…c394
3 touches
1 conflict
0x06cfbc99…0c7b
0x065c9d…c394
2 touches
0 conflicts
0x71942c5c…9ee6
0x065c9d…c394
2 touches
0 conflicts
0xc30d20b6…e00b
0x065c9d…c394
2 touches
0 conflicts
0xdff7720a…7caa
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