← previous blocknext block →recent activity
Analyzing
Block #85,843,170
11 transactions · 9 stateful · 2026-07-05 21:38:46 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,843,170 · 11 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
2w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x409ec225…7f6f
0x065c9d…c394
4 touches
1 conflict
0xdf222f84…4125
0x065c9d…c394
3 touches
1 conflict
0xff5ebb2a…2ca7
0x065c9d…c394
3 touches
1 conflict
0xbbcf38a9…2337
0x065c9d…c394
3 touches
1 conflict
0xd712d2fd…0d2c
0x065c9d…c394
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0xdd70bea3…1ffe
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