← previous blocknext block →recent activity
Analyzing
Block #99,163,914
15 transactions · 15 stateful · 2026-08-25 22:38:02 UTC
Parallelism
87/100
Blocked
13%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,163,914 · 15 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
2w03w04w19w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a4bb2c…f2c7
0x188d58…ea8e
4 touches
1 conflict
0x38aa1898…fdf5
0x3bd359…433a
4 touches
1 conflict
0xd06cc746…27e4
0x5ef52d…4343
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0x388d69c4…4288
0x188d58…ea8e
2 touches
0 conflicts
0xd9a7cef1…1ed5
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0xa5a4bb2c2d…50f2c7
Audit this contract →
← previous block·next block →recent activity