← previous blocknext block →recent activity
Analyzing
Block #86,238,416
24 transactions · 15 stateful · 2026-07-07 17:36:10 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,238,416 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w19w011w116w217w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x006ee1d9…5485
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xbcdee322…f454
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity