Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cc78a11b361ea412ac6eb19091914ea82a587fcd7ce4f1687b81fe826280d8fd

Tx prefix hash: 0d5120545dd9fe854f0d0767321478448cdf80d05c53569c058d43b3b8a957e8
Tx public key: 528d33ff34d234bbd29f8ad411a3503b45507c0e8826f419da245983d2d8a8b9
Timestamp: 1757430996 Timestamp [UCT]: 2025-09-09 15:16:36 Age [y:d:h:m:s]: 00:070:22:51:57
Block: 1364801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50770 RingCT/type: yes/0
Extra: 01528d33ff34d234bbd29f8ad411a3503b45507c0e8826f419da245983d2d8a8b902110000000eb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 012ceb22b234a0aa92107e7dad9c8fe51ce164b762f05aedc17158f726380f9a 0.600000000000 1852840 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1364811, "vin": [ { "gen": { "height": 1364801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "012ceb22b234a0aa92107e7dad9c8fe51ce164b762f05aedc17158f726380f9a" } } ], "extra": [ 1, 82, 141, 51, 255, 52, 210, 52, 187, 210, 159, 138, 212, 17, 163, 80, 59, 69, 80, 124, 14, 136, 38, 244, 25, 218, 36, 89, 131, 210, 216, 168, 185, 2, 17, 0, 0, 0, 14, 178, 247, 132, 196, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8