← previous blocknext block →recent activity
Analyzing
Block #76,090,923
10 transactions · 8 stateful · 2026-05-21 17:35:54 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,090,923 · 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
1w02w13w04w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf9f153d3…a30c
0xa6afd3…d132
4 touches
1 conflict
0x7e390c77…fabc
0x065c9d…c394
3 touches
1 conflict
0x9e9c86a6…a99e
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0002
0x0485a5…81dc
2 touches
0 conflicts
0x00000000…0008
0x0485a5…81dc
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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