Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d55ce24dbe109b48583003b609e1e449f335038a9786ec9f9c2acabd285483

Tx prefix hash: db4ff1f07e71d5494e86f3f6549e16012633e7525faa07150213b9bcd0c4cde6
Tx public key: 4bdf9870539e4c4c70b829ed5a21a289190d9adc32709fce623e281e89f753c6
Timestamp: 1716335961 Timestamp [UCT]: 2024-05-21 23:59:21 Age [y:d:h:m:s]: 00:247:05:20:13
Block: 1027183 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176881 RingCT/type: yes/0
Extra: 014bdf9870539e4c4c70b829ed5a21a289190d9adc32709fce623e281e89f753c602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c495d3ca19c0a883c0a1a7a912a32d605c24f86e7a7a40e710e2b878e4dd060 0.600000000000 1494674 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": 1027193, "vin": [ { "gen": { "height": 1027183 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c495d3ca19c0a883c0a1a7a912a32d605c24f86e7a7a40e710e2b878e4dd060" } } ], "extra": [ 1, 75, 223, 152, 112, 83, 158, 76, 76, 112, 184, 41, 237, 90, 33, 162, 137, 25, 13, 154, 220, 50, 112, 159, 206, 98, 62, 40, 30, 137, 247, 83, 198, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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