← previous blocknext block →recent activity
Analyzing
Block #85,658,868
17 transactions · 15 stateful · 2026-07-05 01:10:13 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,658,868 · 17 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
4w05w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0xc39f192b…2df1
0xd32edf…ff58
3 touches
1 conflict
0x07600609…a932
0x065c9d…c394
2 touches
0 conflicts
0x076b1273…f56d
0x065c9d…c394
2 touches
0 conflicts
0x209e26b9…c9ba
0x065c9d…c394
2 touches
0 conflicts
0x49c531cf…2309
0x065c9d…c394
2 touches
0 conflicts
0x94f0ce58…0861
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