← previous blocknext block →recent activity
Analyzing
Block #101,966,660
20 transactions · 18 stateful · 2026-09-04 18:02:50 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,966,660 · 20 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
1w04w05w16w07w19w110w213w014w115w316w218w019w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab2f6eed…254a
0x188d58…ea8e
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xd06cc746…27e4
0x350035…7777
4 touches
1 conflict
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0xab2f6eed…254c
0x188d58…ea8e
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: Uniswap: PoolManager
3 conflicts on slot 0xab2f6eed4a…68254a
Audit this contract →
← previous block·next block →recent activity