← previous blocknext block →recent activity
Analyzing
Block #76,446,851
13 transactions · 12 stateful · 2026-05-23 09:06:02 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,446,851 · 13 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
3w04w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x8bc3e255…0a0b
0xa6afd3…d132
6 touches
3 conflicts
0x0bd261be…21c6
0xa6afd3…d132
4 touches
1 conflict
0xf62f8b9c…69c1
0xa6afd3…d132
3 touches
1 conflict
0x9b1c8a07…495c
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x3049a91e…a97c
0x0594c7…a3be
2 touches
0 conflicts
0x8c8c7297…574a
0x0594c7…a3be
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity