← previous blocknext block →recent activity
Analyzing
Block #106,569,170
29 transactions · 20 stateful · 2026-09-20 21:21:37 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,569,170 · 29 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
1w05w17w08w211w012w116w218w021w022w223w327w128w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba7d0c8…ec52
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5a6ee6c4…7c39
0xa6afd3…d132
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x36da8334…d363
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: Wrapped Ether (WETH)
1 conflict on slot 0x9ba7d0c85b…06ec52
Audit this contract →
← previous block·next block →recent activity