← previous blocknext block →recent activity
Analyzing
Block #104,160,303
8 transactions · 7 stateful · 2026-09-12 10:50:02 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #104,160,303 · 8 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x86c19788…92bf
0x065c9d…c394
3 touches
1 conflict
0x023cdaef…2140
0x065c9d…c394
3 touches
1 conflict
0xd2356544…37cf
0x065c9d…c394
3 touches
1 conflict
0x6234f622…e05f
0x065c9d…c394
3 touches
1 conflict
0x6f5f4108…ac49
0x065c9d…c394
3 touches
1 conflict
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 0x49cbdb1b43…f7bda4
Audit this contract →
← previous block·next block →recent activity