← previous blocknext block →recent activity
Analyzing
Block #106,473,514
16 transactions · 15 stateful · 2026-09-20 13:20:12 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,473,514 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w28w09w110w011w112w214w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00d8ce35…34f8
0x6f6493…b480
6 touches
3 conflicts
0x042d7f7d…3d5a
0x6f6493…b480
6 touches
3 conflicts
0x0a3c75b6…a6ba
0x6f6493…b480
6 touches
3 conflicts
0x0c17cecb…f5e2
0x6f6493…b480
6 touches
3 conflicts
0x1206d3d6…a9d1
0x6f6493…b480
6 touches
3 conflicts
0x145c899b…7f14
0x6f6493…b480
6 touches
3 conflicts
0x1bc34f81…3768
0x6f6493…b480
6 touches
3 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