← previous blocknext block →recent activity
Analyzing
Block #86,234,605
25 transactions · 22 stateful · 2026-07-07 17:10:45 UTC
Parallelism
80/100
Blocked
45%
Avg conflicts / tx
0.52
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,234,605 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w08w110w012w014w215w017w118w319w422w123w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x006ee1d9…5485
0xa6afd3…d132
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x79e8f935…c3b6
0x34b655…2a6f
4 touches
1 conflict
0xb5a3b1be…8122
0x34b655…2a6f
4 touches
1 conflict
0xc70dd80f…d075
0x34b655…2a6f
4 touches
1 conflict
0xc7178f14…9efb
0x34b655…2a6f
4 touches
1 conflict
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-WETH/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity