← previous blocknext block →recent activity
Analyzing
Block #76,476,675
10 transactions · 8 stateful · 2026-05-23 12:24:36 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,476,675 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x2dc020c7…0697
0xc8689a…ee79
4 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
0xea7ebe9d…709e
0x1d1325…2305
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x877f2b1d…a408
0x34b655…2a6f
4 touches
1 conflict
0x0bd261be…21c6
0xa6afd3…d132
4 touches
1 conflict
0x8bc3e255…0a0b
0xa6afd3…d132
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity