← previous blocknext block →recent activity
Analyzing
Block #76,483,214
11 transactions · 9 stateful · 2026-05-23 13:08:09 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,483,214 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc240a0b0…8afb
0x065c9d…c394
4 touches
1 conflict
0xfcf9b937…26e8
0x065c9d…c394
3 touches
1 conflict
0xab3ff4a4…99eb
0x065c9d…c394
2 touches
0 conflicts
0xd70b5892…5f77
0x065c9d…c394
2 touches
0 conflicts
0xf0d40302…57e6
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity