Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06c72c6549d1dd5d441f17b87ce437587f8075e7ba0720b2934a043e04db7eb7

Tx prefix hash: 1e6ef355656e9e87824b799f5f80fe229eb6a6f229a6abc19c0e34152fdfb913
Tx public key: c534fcbe2be9facb3cb413c1d1635aa5a541741981600b7ee4f1acad2577ea10
Timestamp: 1719411478 Timestamp [UCT]: 2024-06-26 14:17:58 Age [y:d:h:m:s]: 00:294:18:24:52
Block: 1052669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210632 RingCT/type: yes/0
Extra: 01c534fcbe2be9facb3cb413c1d1635aa5a541741981600b7ee4f1acad2577ea100211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7cc314f184f7296a6762efa286551aedaf5d2ee9076c3b098edc8cb54ffe81 0.600000000000 1523000 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": 1052679, "vin": [ { "gen": { "height": 1052669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7cc314f184f7296a6762efa286551aedaf5d2ee9076c3b098edc8cb54ffe81" } } ], "extra": [ 1, 197, 52, 252, 190, 43, 233, 250, 203, 60, 180, 19, 193, 209, 99, 90, 165, 165, 65, 116, 25, 129, 96, 11, 126, 228, 241, 172, 173, 37, 119, 234, 16, 2, 17, 0, 0, 0, 2, 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