← previous blocknext block →recent activity
Analyzing
Block #106,034,267
15 transactions · 15 stateful · 2026-09-19 00:29:31 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,034,267 · 15 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
2w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1adde00d…ed31
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2345695d…3cfd
0xa6afd3…d132
4 touches
1 conflict
0xfdf6dce6…cef1
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0d8d4e5d…2d44
0xa6afd3…d132
3 touches
1 conflict
0xc8a1d58a…ef1e
0xa6afd3…d132
3 touches
1 conflict
0xb05cd4f5…73d0
0x34ae4d…3fc5
2 touches
0 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-WETH/USDC
1 conflict on slot 0x1adde00d4e…1eed31
Audit this contract →
← previous block·next block →recent activity