← previous blocknext block →recent activity
Analyzing
Block #86,447,773
16 transactions · 15 stateful · 2026-07-08 16:54:32 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,447,773 · 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x66c0306f…337e
0x065c9d…c394
2 touches
0 conflicts
0x6ec42950…f534
0x065c9d…c394
2 touches
0 conflicts
0xc34def64…4406
0x065c9d…c394
2 touches
0 conflicts
0xc4f73b16…708a
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