Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60b9de000151d699485b7ba233cec5a98de707dfbfd6909d2c0fa4f2681fd40b

Tx prefix hash: 8be0c9b72c282ee5b96425dd96db645244a5a52cf7984634801e5858bf3b53f2
Tx public key: c2cff72fefb3a38add2afb5366d6cace4310144d9b91ee25f16f0a4a4874036c
Timestamp: 1764780852 Timestamp [UCT]: 2025-12-03 16:54:12 Age [y:d:h:m:s]: 00:018:07:51:28
Block: 1425689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13114 RingCT/type: yes/0
Extra: 01c2cff72fefb3a38add2afb5366d6cace4310144d9b91ee25f16f0a4a4874036c021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26a94c700f39e0c89292fd7dac721ecd4e20cae10495007fc532d634e8491f78 0.600000000000 1914354 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": 1425699, "vin": [ { "gen": { "height": 1425689 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26a94c700f39e0c89292fd7dac721ecd4e20cae10495007fc532d634e8491f78" } } ], "extra": [ 1, 194, 207, 247, 47, 239, 179, 163, 138, 221, 42, 251, 83, 102, 214, 202, 206, 67, 16, 20, 77, 155, 145, 238, 37, 241, 111, 10, 74, 72, 116, 3, 108, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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