← previous blocknext block →recent activity
Analyzing
Block #97,386,089
8 transactions · 7 stateful · 2026-08-19 16:06:09 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,386,089 · 8 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x169d60cf…e576
0xa6afd3…d132
4 touches
1 conflict
0x3199a6b2…eb67
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0ff724dc…31b3
0xa6afd3…d132
3 touches
1 conflict
0x610c766e…f3b6
0xa6afd3…d132
3 touches
1 conflict
0x1a4a34b2…4a40
0xd32edf…ff58
3 touches
1 conflict
0x55012d1a…3907
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
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 0x169d60cf7d…a1e576
Audit this contract →
← previous block·next block →recent activity