Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46581f5b5b8ff81bf56bb169128e987763859c41e33c373c2407e0acfba25bdf

Tx prefix hash: 548ad4e24ad84143eeb73bafd315beb1157cd02dc0c8b05103c8c3932ce5e24e
Tx public key: c8a052767dd17001a003b4b9ec00010185f32d6d5895533b942f0c9df4887e47
Timestamp: 1719178242 Timestamp [UCT]: 2024-06-23 21:30:42 Age [y:d:h:m:s]: 00:327:07:49:09
Block: 1050733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233932 RingCT/type: yes/0
Extra: 01c8a052767dd17001a003b4b9ec00010185f32d6d5895533b942f0c9df4887e4702110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9170c829a6a375e72b0503d6bcc6f5cc0a2cc32275dc9532f14da381e81799c 0.600000000000 1520908 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": 1050743, "vin": [ { "gen": { "height": 1050733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9170c829a6a375e72b0503d6bcc6f5cc0a2cc32275dc9532f14da381e81799c" } } ], "extra": [ 1, 200, 160, 82, 118, 125, 209, 112, 1, 160, 3, 180, 185, 236, 0, 1, 1, 133, 243, 45, 109, 88, 149, 83, 59, 148, 47, 12, 157, 244, 136, 126, 71, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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