← previous blocknext block →recent activity
Analyzing
Block #96,838,173
12 transactions · 12 stateful · 2026-08-17 17:40:47 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,838,173 · 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
1w02w16w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x07969058…0fef
0x34b655…2a6f
2 touches
0 conflicts
0x0c7441d3…34fc
0x34b655…2a6f
2 touches
0 conflicts
0x1ffa9f70…0e39
0x34b655…2a6f
2 touches
0 conflicts
0x3f92891d…fcde
0x34b655…2a6f
2 touches
0 conflicts
0x4067b2e9…83f6
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity