← previous blocknext block →recent activity
Analyzing
Block #85,220,650
15 transactions · 15 stateful · 2026-07-03 00:31:59 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,220,650 · 15 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
1w06w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0x27dfde00…3670
0x065c9d…c394
4 touches
1 conflict
0x6497d6ea…0654
0x065c9d…c394
3 touches
1 conflict
0x35b2c47a…bc91
0x065c9d…c394
2 touches
0 conflicts
0x681186ed…f72a
0x065c9d…c394
2 touches
0 conflicts
0x7fd4bd98…5682
0x065c9d…c394
2 touches
0 conflicts
0x94afd3b5…0c9a
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