← previous blocknext block →recent activity
Analyzing
Block #104,333,055
36 transactions · 35 stateful · 2026-09-13 01:26:29 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #104,333,055 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w510w011w217w318w120w221w325w226w327w431w333w634w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x52e69143…95ad
0x065c9d…c394
8 touches
6 conflicts
0x758a0dd5…0f46
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0xb27b8349…5ea2
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x7565ee79…de34
0xd32edf…ff58
7 touches
6 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity