← previous blocknext block →recent activity
Analyzing
Block #97,356,002
11 transactions · 11 stateful · 2026-08-19 13:26:03 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,356,002 · 11 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
2w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fffa5c0…a3a9
0xa6afd3…d132
4 touches
1 conflict
0x0b2ae7be…fede
0x34b655…2a6f
4 touches
1 conflict
0x731f2745…9370
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0236cc3b…c9da
0xa6afd3…d132
3 touches
1 conflict
0x10abefc9…c9bc
0x2b46c0…1669
2 touches
0 conflicts
0x10d80fee…dbda
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 0x0fffa5c054…49a3a9
Audit this contract →
← previous block·next block →recent activity