← previous blocknext block →recent activity
Analyzing
Block #85,198,743
12 transactions · 11 stateful · 2026-07-02 22:06:06 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,198,743 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cec275e…33dc
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5a03a868…c218
0x065c9d…c394
3 touches
1 conflict
0xb39b07ee…53ed
0x065c9d…c394
3 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x06aed19e…ca57
0x34b655…2a6f
2 touches
0 conflicts
0x29a71889…a248
0x34b655…2a6f
2 touches
0 conflicts
0x4e12e525…93e9
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 0x4cec275e5c…7333dc
Audit this contract →
← previous block·next block →recent activity