← previous blocknext block →recent activity
Analyzing
Block #102,055,631
20 transactions · 17 stateful · 2026-09-05 01:33:43 UTC
Parallelism
90/100
Blocked
12%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,055,631 · 20 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
1w02w13w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7920dc0c…eae2
0x188d58…ea8e
4 touches
1 conflict
0xedbb33ba…133e
0x188d58…ea8e
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1342557a…df31
0xebb5a0…71fa
4 touches
1 conflict
0x6bc33bdb…4bd1
0xebb5a0…71fa
4 touches
1 conflict
0x365613d8…f2c0
0x065c9d…c394
4 touches
1 conflict
0x38aa1898…fdf5
0xfbc1f8…8f9e
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 0x7920dc0c62…f6eae2
Audit this contract →
← previous block·next block →recent activity