← previous blocknext block →recent activity
Analyzing
Block #99,660,574
15 transactions · 15 stateful · 2026-08-27 16:25:11 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,660,574 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w17w08w110w211w113w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03e5b578…2fec
0xa6afd3…d132
4 touches
1 conflict
0xc26c0c87…c857
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xcad937e9…7870
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: Kuru Exchange: Market-WETH/USDC
1 conflict on slot 0x03e5b57848…af2fec
Audit this contract →
← previous block·next block →recent activity