← previous blocknext block →recent activity
Analyzing
Block #103,213,643
11 transactions · 10 stateful · 2026-09-09 03:06:50 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,213,643 · 11 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
1w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x029ce6eb…8b11
0x065c9d…c394
2 touches
0 conflicts
0x06e377e6…77be
0x065c9d…c394
2 touches
0 conflicts
0x24b73270…1a64
0x065c9d…c394
2 touches
0 conflicts
0x2bb9e2a6…e161
0x065c9d…c394
2 touches
0 conflicts
0x71a0f025…0b6e
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 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity