← previous blocknext block →recent activity
Analyzing
Block #85,219,214
18 transactions · 15 stateful · 2026-07-03 00:22:26 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,219,214 · 18 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
1w010w114w015w1
- 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
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x12cbae4c…68f3
0x065c9d…c394
2 touches
0 conflicts
0x5dabed30…5df6
0x065c9d…c394
2 touches
0 conflicts
0x7839019f…a2f5
0x065c9d…c394
2 touches
0 conflicts
0x9d7cc31e…8f66
0x065c9d…c394
2 touches
0 conflicts
0x9fc757a3…cd4c
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