← previous blocknext block →recent activity
Analyzing
Block #99,778,853
22 transactions · 16 stateful · 2026-08-28 02:24:11 UTC
Parallelism
91/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,778,853 · 22 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
3w04w05w117w018w019w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f7e3b7…e015
0x188d58…ea8e
4 touches
1 conflict
0x00f7e3b7…e016
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb86
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
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
1 conflict on slot 0x00f7e3b74f…eee015
Audit this contract →
← previous block·next block →recent activity