← previous blocknext block →recent activity
Analyzing
Block #86,566,094
14 transactions · 12 stateful · 2026-07-09 06:06:02 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,566,094 · 14 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
1w02w17w09w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc0eb79d1…29a4
0x34b655…2a6f
4 touches
1 conflict
0xbf948ca2…7ed8
0xd32edf…ff58
3 touches
1 conflict
0x1a871184…9a08
0x065c9d…c394
2 touches
0 conflicts
0x1fba13a6…23f3
0x065c9d…c394
2 touches
0 conflicts
0x39b387f9…fc85
0x065c9d…c394
2 touches
0 conflicts
0x54540049…2247
0x065c9d…c394
2 touches
0 conflicts
0xa8f32a1c…78f5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity