← previous blocknext block →recent activity
Analyzing
Block #102,275,322
11 transactions · 11 stateful · 2026-09-05 20:07:21 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,275,322 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b9e2d47…9675
0x188d58…ea8e
4 touches
1 conflict
0x65ff54af…aa01
0x34b655…2a6f
4 touches
1 conflict
0xa0b999d5…5758
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x17359e55…7914
0x188d58…ea8e
4 touches
1 conflict
0x1342557a…df31
0x27bc99…9a93
4 touches
1 conflict
0x38aa1898…fdf5
0xb53c4f…8a01
4 touches
1 conflict
0xb3dee783…2711
0x27bc99…9a93
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
1 conflict on slot 0x8b9e2d473e…1c9675
Audit this contract →
← previous block·next block →recent activity