← previous blocknext block →recent activity
Analyzing
Block #86,243,379
16 transactions · 12 stateful · 2026-07-07 18:09:21 UTC
Parallelism
81/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,243,379 · 16 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
1w02w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0xc1260298…e0b0
0xd32edf…ff58
3 touches
1 conflict
0x11d209a6…444e
0x065c9d…c394
2 touches
0 conflicts
0x329c1b10…ca27
0x065c9d…c394
2 touches
0 conflicts
0x6a92942d…a567
0x065c9d…c394
2 touches
0 conflicts
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0xe3804d24…baa0
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