← previous blocknext block →recent activity
Analyzing
Block #76,223,070
17 transactions · 13 stateful · 2026-05-22 08:15:55 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,223,070 · 17 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
1w04w15w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb9d8189…e926
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x7e002808…db6f
0x065c9d…c394
2 touches
0 conflicts
0xb81da9cf…7809
0x065c9d…c394
2 touches
0 conflicts
0xd95a3347…2cb7
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
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 0xdb9d8189a0…88e926
Audit this contract →
← previous block·next block →recent activity