← previous blocknext block →recent activity
Analyzing
Block #86,134,768
18 transactions · 15 stateful · 2026-07-07 06:04:10 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,134,768 · 18 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
1w03w04w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x28651a33…a08c
0x065c9d…c394
2 touches
0 conflicts
0x3ed42985…aeed
0x065c9d…c394
2 touches
0 conflicts
0x88a56e89…0693
0x065c9d…c394
2 touches
0 conflicts
0x9d1566e1…186f
0x065c9d…c394
2 touches
0 conflicts
0xb703c6aa…f030
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
1 conflict on slot 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity