← previous blocknext block →recent activity
Analyzing
Block #85,914,302
23 transactions · 14 stateful · 2026-07-06 05:32:38 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.17
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,914,302 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w210w013w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0x33e3dcdd…1f1f
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x9fc8b97d…96da
0x2a68ba…90c5
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
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