← previous blocknext block →recent activity
Analyzing
Block #97,628,738
15 transactions · 14 stateful · 2026-08-20 12:45:49 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,628,738 · 15 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
1w02w13w18w09w211w314w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aa7a878…0103
0xa6afd3…d132
6 touches
3 conflicts
0xc2044b9c…c271
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x37699b20…1072
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 0x6aa7a878c0…ea0103
Audit this contract →
← previous block·next block →recent activity