← previous blocknext block →recent activity
Analyzing
Block #85,373,458
9 transactions · 7 stateful · 2026-07-03 17:29:56 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,373,458 · 9 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0ca0567…3507
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf467ed76…e645
0x065c9d…c394
3 touches
1 conflict
0x214da01a…2f3e
0x065c9d…c394
3 touches
1 conflict
0x7768f8a8…1597
0x065c9d…c394
3 touches
1 conflict
0xa4564575…389e
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x0eac6378…36f4
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 0xb0ca056765…b83507
Audit this contract →
← previous block·next block →recent activity