← previous blocknext block →recent activity
Analyzing
Block #106,916,394
14 transactions · 14 stateful · 2026-09-22 02:30:15 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,916,394 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w18w09w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8514b614…35a9
0xa6afd3…d132
4 touches
1 conflict
0x050d7a8a…67d0
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x63b90da2…4b0c
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…8313
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4dc884eb…e337
0xa6afd3…d132
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-WETH/USDC
1 conflict on slot 0x8514b61411…5635a9
Audit this contract →
← previous block·next block →recent activity