← previous blocknext block →recent activity
Analyzing
Block #76,506,866
6 transactions · 6 stateful · 2026-05-23 15:45:40 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,506,866 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0xc906436c…b676
0xa6afd3…d132
4 touches
1 conflict
0x3907f0fa…3359
0xa6afd3…d132
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18db33bc…0b80
0x065c9d…c394
2 touches
0 conflicts
0x3bc9723e…4dcf
0x065c9d…c394
2 touches
0 conflicts
0x5bc430f1…9f37
0x065c9d…c394
2 touches
0 conflicts
0x7dd919e9…85f6
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: MarginAccount
1 conflict on slot 0x99a2130578…57dffc
Audit this contract →
← previous block·next block →recent activity