← previous blocknext block →recent activity
Analyzing
Block #92,528,914
13 transactions · 11 stateful · 2026-08-02 15:50:59 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,528,914 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x729c91b8…9539
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x729c91b8…9537
0x188d58…ea8e
4 touches
1 conflict
0x56a919c4…ab49
0xee8c0e…1242
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0x729c91b8a3…e19539
Audit this contract →
← previous block·next block →recent activity