← previous blocknext block →recent activity
Analyzing
Block #86,358,361
14 transactions · 13 stateful · 2026-07-08 06:57:09 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,358,361 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w39w410w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
6 touches
3 conflicts
0x683be569…5d64
0x065c9d…c394
4 touches
1 conflict
0x4db4c3db…a325
0x40c49f…2af0
2 touches
0 conflicts
0x93f73d88…eb97
0x40c49f…2af0
2 touches
0 conflicts
0xee8489a5…ca13
0x40c49f…2af0
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity