← previous blocknext block →recent activity
Analyzing
Block #76,462,644
21 transactions · 17 stateful · 2026-05-23 10:51:04 UTC
Parallelism
90/100
Blocked
24%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,462,644 · 21 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
1w03w14w17w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xce569d27…1a88
0xd32edf…ff58
3 touches
1 conflict
0x8b91d4dd…cd23
0x065c9d…c394
2 touches
0 conflicts
0xa7413f50…d17f
0x065c9d…c394
2 touches
0 conflicts
0xb4634fdc…4029
0x065c9d…c394
2 touches
0 conflicts
0xbec554ec…412a
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity