← previous blocknext block →recent activity
Analyzing
Block #76,483,046
11 transactions · 9 stateful · 2026-05-23 13:07:02 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,483,046 · 11 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
1w02w03w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x68624fca…70bf
0x065c9d…c394
2 touches
0 conflicts
0x91b6c38d…fcbc
0x065c9d…c394
2 touches
0 conflicts
0xaf3fc3fb…05f3
0x065c9d…c394
2 touches
0 conflicts
0xb2022931…1787
0x065c9d…c394
2 touches
0 conflicts
0xe4381538…2a96
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 0x18cf3003ed…9951d1
Audit this contract →
← previous block·next block →recent activity