Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41519b8d1780984851ac99eaa3b8c973100877f46a218feee8edd20e6142883c

Tx prefix hash: 3ba4aa4258fab6b95911c0ca6246d3918b57378f1df2003f4d0289570d4bae04
Tx public key: 784907b07d4a4bc40540df864933492a2eb2eef7f12e86a7e9cb0bca3461d2b6
Timestamp: 1581746929 Timestamp [UCT]: 2020-02-15 06:08:49 Age [y:d:h:m:s]: 04:318:10:46:43
Block: 65498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119641 RingCT/type: yes/0
Extra: 01784907b07d4a4bc40540df864933492a2eb2eef7f12e86a7e9cb0bca3461d2b60211000000058a2ee0d9000000000000000000

1 output(s) for total of 372.392782823000 dcy

stealth address amount amount idx
00: 4284cd9eab7ccb486e0156209d33f221d9a2acd775dc89eedd6b12de4e66a440 372.392782823000 120759 of 0

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": 65508, "vin": [ { "gen": { "height": 65498 } } ], "vout": [ { "amount": 372392782823, "target": { "key": "4284cd9eab7ccb486e0156209d33f221d9a2acd775dc89eedd6b12de4e66a440" } } ], "extra": [ 1, 120, 73, 7, 176, 125, 74, 75, 196, 5, 64, 223, 134, 73, 51, 73, 42, 46, 178, 238, 247, 241, 46, 134, 167, 233, 203, 11, 202, 52, 97, 210, 182, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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