← previous blocknext block →recent activity
Analyzing
Block #106,186,929
11 transactions · 11 stateful · 2026-09-19 13:17:48 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,186,929 · 11 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
1w04w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb52f8e91…12e4
0xa6afd3…d132
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x62d5dc0a…3e26
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2517e85a…1750
0xa6afd3…d132
4 touches
1 conflict
0x797ee54e…d08d
0xa6afd3…d132
3 touches
1 conflict
0x8e1f2058…afee
0xa6afd3…d132
3 touches
1 conflict
0x8cf3d245…1d0d
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 0xb52f8e9198…1512e4
Audit this contract →
← previous block·next block →recent activity