← previous blocknext block →recent activity
Analyzing
Block #101,673,627
18 transactions · 16 stateful · 2026-09-03 17:25:43 UTC
Parallelism
72/100
Blocked
38%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,673,627 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w28w311w415w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
8 touches
6 conflicts
0xf9da5665…2703
0x754704…b603
6 touches
3 conflicts
0x846f2172…fd54
0x0555e3…2b9c
6 touches
3 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
6 touches
3 conflicts
0x00000000…0000
0x2d82ac…5fd8
6 touches
3 conflicts
0x00000000…0001
0x2d82ac…5fd8
6 touches
3 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: Uniswap: PoolManager
10 conflicts on slot 0x01e7b86585…4d6e6d
Audit this contract →
← previous block·next block →recent activity