← previous blocknext block →recent activity
Analyzing
Block #97,568,080
21 transactions · 20 stateful · 2026-08-20 07:39:15 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,568,080 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w18w010w213w314w015w119w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22414fbb…1edf
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xe2457683…1957
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…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
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 0x22414fbb6f…e41edf
Audit this contract →
← previous block·next block →recent activity