Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14d5a1a4b9d73c62e810598b4b035d6d8f53d4bb4345bce3456ab5b4ae440873

Tx prefix hash: 58826e4b231285181f4e066e9f0f0f50cd663aec92d13701d7608737c7babc87
Tx public key: 538f3c651db5ed47a4bbe5fc3e95911d452b23e7b964954b49cb9c8bf5a644b7
Timestamp: 1713698895 Timestamp [UCT]: 2024-04-21 11:28:15 Age [y:d:h:m:s]: 01:023:13:22:21
Block: 1005313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277796 RingCT/type: yes/0
Extra: 01538f3c651db5ed47a4bbe5fc3e95911d452b23e7b964954b49cb9c8bf5a644b70211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40234937940114364d86aecf9c7542ec7714568dec02ce180946677db4bb8b14 0.600000000000 1465899 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": 1005323, "vin": [ { "gen": { "height": 1005313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40234937940114364d86aecf9c7542ec7714568dec02ce180946677db4bb8b14" } } ], "extra": [ 1, 83, 143, 60, 101, 29, 181, 237, 71, 164, 187, 229, 252, 62, 149, 145, 29, 69, 43, 35, 231, 185, 100, 149, 75, 73, 203, 156, 139, 245, 166, 68, 183, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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