Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c42ab431942f7bd66e14384b1ec5d3f416d9246e6bee67c3d14cb973f7e5a3e4

Tx prefix hash: a0e6a25b6fbc316a2b9af9525ac38143b21b1d818629470ddc4d7ea9a366ce25
Tx public key: 934379ba321105e6fdc59b2985006765707d3d0b5a8a853dd00338fcc70f3fec
Timestamp: 1708559803 Timestamp [UCT]: 2024-02-21 23:56:43 Age [y:d:h:m:s]: 01:304:13:42:34
Block: 962714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476469 RingCT/type: yes/0
Extra: 01934379ba321105e6fdc59b2985006765707d3d0b5a8a853dd00338fcc70f3fec02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160dee4ea92655e737cc0d3326e828ba14412c62914b7cc7e33d6a0506a0f66b 0.600000000000 1422397 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": 962724, "vin": [ { "gen": { "height": 962714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160dee4ea92655e737cc0d3326e828ba14412c62914b7cc7e33d6a0506a0f66b" } } ], "extra": [ 1, 147, 67, 121, 186, 50, 17, 5, 230, 253, 197, 155, 41, 133, 0, 103, 101, 112, 125, 61, 11, 90, 138, 133, 61, 208, 3, 56, 252, 199, 15, 63, 236, 2, 17, 0, 0, 0, 2, 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