← previous blocknext block →recent activity
Analyzing
Block #105,851,915
16 transactions · 15 stateful · 2026-09-18 09:10:42 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,851,915 · 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
1w03w04w16w07w18w010w211w112w013w114w215w1
- 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
0x8a3fecf6…b414
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0bc80bb4…a97c
0x851145…3f07
4 touches
1 conflict
0x47b3f3d4…8d09
0x851145…3f07
4 touches
1 conflict
0xc0364fa8…181e
0x851145…3f07
4 touches
1 conflict
0x4213f1c0…219a
0x2a68ba…90c5
4 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity