← previous blocknext block →recent activity
Analyzing
Block #85,187,343
16 transactions · 16 stateful · 2026-07-02 20:50:11 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,187,343 · 16 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
1w02w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf5540a6a…024b
0xa6afd3…d132
3 touches
1 conflict
0x3833c9c9…14dd
0x1111b3…4111
2 touches
0 conflicts
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
2 touches
0 conflicts
0xb5b71470…8bb8
0x754704…b603
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 0x9ff176a9ad…67152e
Audit this contract →
← previous block·next block →recent activity