Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1477413998422598b090ba1775f7725bcec89d2a24e9d2cb2fd52f8ef125e9cc

Tx prefix hash: f63d4dd3a9243b6e464ebcf31a37a3a69571a1ac8f34279b8a701369565c3501
Tx public key: 2de8aeaacbc85f9501cedc77f3a1cdb43f05c8b7ff85e716625845121b0d4e4f
Timestamp: 1760969030 Timestamp [UCT]: 2025-10-20 14:03:50 Age [y:d:h:m:s]: 00:104:19:06:57
Block: 1394116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74828 RingCT/type: yes/0
Extra: 012de8aeaacbc85f9501cedc77f3a1cdb43f05c8b7ff85e716625845121b0d4e4f021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cdd3e0c19df633dfe55a7d59148493a50575c7f47578d0b9b11a7ba1741e2ab 0.600000000000 1882383 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": 1394126, "vin": [ { "gen": { "height": 1394116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cdd3e0c19df633dfe55a7d59148493a50575c7f47578d0b9b11a7ba1741e2ab" } } ], "extra": [ 1, 45, 232, 174, 170, 203, 200, 95, 149, 1, 206, 220, 119, 243, 161, 205, 180, 63, 5, 200, 183, 255, 133, 231, 22, 98, 88, 69, 18, 27, 13, 78, 79, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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