← previous blocknext block →recent activity
Analyzing
Block #76,224,482
7 transactions · 7 stateful · 2026-05-22 08:25:29 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,224,482 · 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
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x11e215da…2be8
0x065c9d…c394
2 touches
0 conflicts
0x7f75d1b2…09f0
0x065c9d…c394
2 touches
0 conflicts
0x94f4f59f…169e
0x065c9d…c394
2 touches
0 conflicts
0xcff8e153…3578
0x065c9d…c394
2 touches
0 conflicts
0xd5393ac9…33e7
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