← previous blocknext block →recent activity
Analyzing
Block #86,357,454
19 transactions · 16 stateful · 2026-07-08 06:51:05 UTC
Parallelism
84/100
Blocked
13%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,357,454 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x0b5df9ec…6728
0x065c9d…c394
3 touches
1 conflict
0x33f6bb8e…43d8
0x065c9d…c394
2 touches
0 conflicts
0x40bb0d95…9292
0x065c9d…c394
2 touches
0 conflicts
0x5c6c5ad9…39e0
0x065c9d…c394
2 touches
0 conflicts
0x5cbfd9f0…347e
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity