← previous blocknext block →recent activity
Analyzing
Block #76,448,959
21 transactions · 18 stateful · 2026-05-23 09:20:03 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,448,959 · 21 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
1w04w15w08w09w110w211w313w115w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 conflicts
0x0969f9bb…dbec
0xd32edf…ff58
7 touches
6 conflicts
0x0bd261be…21c6
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0xe5957f08…90b5
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
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: MarginAccount
6 conflicts on slot 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity