← previous blocknext block →recent activity
Analyzing
Block #102,276,014
26 transactions · 25 stateful · 2026-09-05 20:10:52 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,276,014 · 26 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
1w02w13w04w15w06w27w08w311w016w017w119w020w122w224w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17359e55…7914
0x188d58…ea8e
8 touches
6 conflicts
0x8b9e2d47…9675
0x188d58…ea8e
8 touches
6 conflicts
0x1342557a…df31
0x27bc99…9a93
8 touches
6 conflicts
0xb3dee783…2711
0x27bc99…9a93
8 touches
6 conflicts
0x38aa1898…fdf5
0xb53c4f…8a01
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0xd0ec60a1…d240
0x1b6862…e19c
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 0x17359e55e7…a57914
Audit this contract →
← previous block·next block →recent activity