← previous blocknext block →recent activity
Analyzing
Block #76,260,238
10 transactions · 8 stateful · 2026-05-22 12:23:29 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,260,238 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf85c75bc…00b5
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8f6f13d2…efa0
0x0a4fcb…a602
2 touches
0 conflicts
0x8f6f13d2…efa6
0x0a4fcb…a602
2 touches
0 conflicts
0x8f6f13d2…efa7
0x0a4fcb…a602
2 touches
0 conflicts
0x8f6f13d2…efa8
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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 0xf85c75bcf3…1f00b5
Audit this contract →
← previous block·next block →recent activity