← previous blocknext block →recent activity
Analyzing
Block #76,244,506
7 transactions · 5 stateful · 2026-05-22 10:38:56 UTC
Parallelism
57/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,244,506 · 7 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x132712a5…8f52
0x065c9d…c394
2 touches
0 conflicts
0x1d296631…79fe
0x065c9d…c394
2 touches
0 conflicts
0xa98c83a6…a65b
0x065c9d…c394
2 touches
0 conflicts
0xab422503…21d2
0x065c9d…c394
2 touches
0 conflicts
0xcdd4bbf0…76e1
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-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity