Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc77fdcd3e9bd378d5e4449a33511ad84e5e283b8be06d6a57dadd8d26c4f219

Tx prefix hash: e9211e7fd7a3bb6b56ae6d7efc1b2f4585f63d54f5592ba801a729551c06150b
Tx public key: 459664c3e0cf37af2279276ba1ebaf9e460d15c29e2e9e0c54b85d7f240c0e93
Timestamp: 1755498001 Timestamp [UCT]: 2025-08-18 06:20:01 Age [y:d:h:m:s]: 00:091:15:05:11
Block: 1349010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65349 RingCT/type: yes/0
Extra: 01459664c3e0cf37af2279276ba1ebaf9e460d15c29e2e9e0c54b85d7f240c0e93021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9506ae7514e7825de9b3a74e52fb91950661d2db9aead2b7972f49cfb573f3b2 0.600000000000 1836939 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": 1349020, "vin": [ { "gen": { "height": 1349010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9506ae7514e7825de9b3a74e52fb91950661d2db9aead2b7972f49cfb573f3b2" } } ], "extra": [ 1, 69, 150, 100, 195, 224, 207, 55, 175, 34, 121, 39, 107, 161, 235, 175, 158, 70, 13, 21, 194, 158, 46, 158, 12, 84, 184, 93, 127, 36, 12, 14, 147, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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