← previous blocknext block →recent activity
Analyzing
Block #97,535,080
26 transactions · 20 stateful · 2026-08-20 04:51:38 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,535,080 · 26 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
1w02w04w05w110w011w114w015w016w117w118w219w221w022w125w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1203ea08…52c3
0xa6afd3…d132
6 touches
3 conflicts
0x18865c9d…8ced
0xa6afd3…d132
6 touches
3 conflicts
0x8902ba1f…f4b6
0x34b655…2a6f
6 touches
3 conflicts
0x8518cac0…d3f6
0xa6afd3…d132
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x98067f20…59e4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity