← previous blocknext block →recent activity
Analyzing
Block #76,462,372
10 transactions · 10 stateful · 2026-05-23 10:49:17 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,462,372 · 10 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
1w02w13w24w25w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x1702054a…fa91
0x065c9d…c394
2 touches
0 conflicts
0x2f011ac7…30fb
0x065c9d…c394
2 touches
0 conflicts
0x57dbd813…17e7
0x065c9d…c394
2 touches
0 conflicts
0xc240a0b0…8afb
0x065c9d…c394
2 touches
0 conflicts
0xf9dd424e…4cf3
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