← previous blocknext block →recent activity
Analyzing
Block #105,921,828
27 transactions · 23 stateful · 2026-09-18 15:03:27 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,921,828 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w18w116w017w218w019w220w321w325w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3a429191…9cda
0x34b655…2a6f
6 touches
3 conflicts
0x375b6201…9c1e
0x34b655…2a6f
4 touches
1 conflict
0x7fd8d2a4…d426
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x9846449a…467e
0x34b655…2a6f
4 touches
1 conflict
0xaa9769ec…a2f5
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity