← previous blocknext block →recent activity
Analyzing
Block #85,173,246
16 transactions · 14 stateful · 2026-07-02 19:16:15 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,173,246 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w09w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x657800eb…8b0f
0x065c9d…c394
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf76fd3e7…53cc
0x754704…b603
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xc8c39eb0…38c9
0x754704…b603
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
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
3 conflicts on slot 0x657800ebdf…258b0f
Audit this contract →
← previous block·next block →recent activity