← previous blocknext block →recent activity
Analyzing
Block #93,683,197
22 transactions · 19 stateful · 2026-08-06 16:38:31 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,683,197 · 22 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
1w02w15w012w113w014w115w216w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89678d1b…463e
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x439cfb2c…7b9e
0xa6afd3…d132
6 touches
3 conflicts
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…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
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 0x89678d1b59…5a463e
Audit this contract →
← previous block·next block →recent activity