← previous blocknext block →recent activity
Analyzing
Block #96,639,308
12 transactions · 11 stateful · 2026-08-17 01:00:34 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,639,308 · 12 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2adbfc13…e36d
0xa6afd3…d132
3 touches
1 conflict
0x4b7c95d9…136e
0xa6afd3…d132
2 touches
1 conflict
0x8919f6fe…07e8
0xa6afd3…d132
2 touches
1 conflict
0x0bd95eb4…e562
0x34b655…2a6f
2 touches
0 conflicts
0x286ff32c…2782
0x34b655…2a6f
2 touches
0 conflicts
0x3a37aad1…720f
0x34b655…2a6f
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 0x3464bbc5a6…fba323
Audit this contract →
← previous block·next block →recent activity