← previous blocknext block →recent activity
Analyzing
Block #76,166,977
15 transactions · 12 stateful · 2026-05-22 02:02:29 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,166,977 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w39w410w011w1
- 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
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0x44ad89ba…cf83
0x25d593…7777
4 touches
1 conflict
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