← previous blocknext block →recent activity
Analyzing
Block #93,499,168
23 transactions · 21 stateful · 2026-08-06 01:13:24 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,499,168 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w18w012w113w214w015w116w317w218w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xa1ff0729…0146
0xa6afd3…d132
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x890a1db9…1712
0xa6afd3…d132
6 touches
3 conflicts
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
0x66b45d1e…7a41
0x34b655…2a6f
4 touches
1 conflict
0x6767539b…f211
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity