← previous blocknext block →recent activity
Analyzing
Block #102,560,726
31 transactions · 26 stateful · 2026-09-06 20:13:46 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,560,726 · 31 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
1w02w13w24w38w012w013w115w224w225w326w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc84f8c5f…631e
0x188d58…ea8e
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0x38aa1898…fdf5
0x27c8b4…6b01
8 touches
6 conflicts
0x467dfc1b…6cc7
0x27bc99…9a93
8 touches
6 conflicts
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0x99c1bf22…c21d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0xc84f8c5f33…b5631e
Audit this contract →
← previous block·next block →recent activity