Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c22939508fd29a12d15233aadfc54129e6c3cd7d8b27c2a023b859f61a300e47

Tx prefix hash: a0c03d09abc39b951a664dc450759de33809bdf62846fcf24db207d907884da4
Tx public key: 9e4e941c19bf81bc3be0cefda97d6ae5da823e82e68e610e9fdb0ace682b95c8
Timestamp: 1726361109 Timestamp [UCT]: 2024-09-15 00:45:09 Age [y:d:h:m:s]: 00:205:11:23:30
Block: 1110289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146673 RingCT/type: yes/0
Extra: 019e4e941c19bf81bc3be0cefda97d6ae5da823e82e68e610e9fdb0ace682b95c802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6243063d87e8ae75965bedf31405c820b81ff4d09e7134210c2f5ad82164558 0.600000000000 1588842 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": 1110299, "vin": [ { "gen": { "height": 1110289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6243063d87e8ae75965bedf31405c820b81ff4d09e7134210c2f5ad82164558" } } ], "extra": [ 1, 158, 78, 148, 28, 25, 191, 129, 188, 59, 224, 206, 253, 169, 125, 106, 229, 218, 130, 62, 130, 230, 142, 97, 14, 159, 219, 10, 206, 104, 43, 149, 200, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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