Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a31b1a9e84699640ee2a1ea9363c9308efd0cfaf1be5080891916c30b1b5b2

Tx prefix hash: a662b78ea539aae27dd167ec5425e72279acebe6bda73e77d3134f77e7025ab1
Tx public key: 9c5bb2da61c0178a4001d8fef850921b36688a283b5049b1a5d19e50a309e202
Timestamp: 1706976756 Timestamp [UCT]: 2024-02-03 16:12:36 Age [y:d:h:m:s]: 01:083:20:50:56
Block: 949567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321035 RingCT/type: yes/0
Extra: 019c5bb2da61c0178a4001d8fef850921b36688a283b5049b1a5d19e50a309e2020211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19da5f641868a4bdad2b8520c130b4ec6d0fc4b244099efad1ff202483edce55 0.600000000000 1408097 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": 949577, "vin": [ { "gen": { "height": 949567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19da5f641868a4bdad2b8520c130b4ec6d0fc4b244099efad1ff202483edce55" } } ], "extra": [ 1, 156, 91, 178, 218, 97, 192, 23, 138, 64, 1, 216, 254, 248, 80, 146, 27, 54, 104, 138, 40, 59, 80, 73, 177, 165, 209, 158, 80, 163, 9, 226, 2, 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