← previous blocknext block →recent activity
Analyzing
Block #95,707,384
28 transactions · 26 stateful · 2026-08-13 18:52:10 UTC
Parallelism
82/100
Blocked
54%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,707,384 · 28 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
1w02w03w14w25w16w27w38w39w013w114w215w017w319w420w225w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0xe75ce681…ba60
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xb0e4f69d…34e6
0x1b6862…e19c
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
3 conflicts on slot 0xe75ce68176…09ba5f
Audit this contract →
← previous block·next block →recent activity