← previous blocknext block →recent activity
Analyzing
Block #104,984,146
18 transactions · 18 stateful · 2026-09-15 08:21:40 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,984,146 · 18 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
1w05w16w07w112w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x392d9063…a648
0x065c9d…c394
2 touches
0 conflicts
0x6923bf18…ba1a
0x065c9d…c394
2 touches
0 conflicts
0xa1c1e993…bb71
0x065c9d…c394
2 touches
0 conflicts
0xa41d45bb…647b
0x065c9d…c394
2 touches
0 conflicts
0xc8cd0094…8294
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