Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ddf781189eac0bf50024657b4f3adfd224a87af1236b33f4ef797c9bbc4ac9

Tx prefix hash: 493bbfb25a136513a48aabbe9b4b4d3b5a57a5ced565dd5792186af7aa5427ce
Tx public key: 2cbd822d7095e36b44450a7dd02d231eb1442021c978d9acc12b6f88252618e6
Timestamp: 1684893986 Timestamp [UCT]: 2023-05-24 02:06:26 Age [y:d:h:m:s]: 01:320:18:02:34
Block: 766760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490446 RingCT/type: yes/0
Extra: 012cbd822d7095e36b44450a7dd02d231eb1442021c978d9acc12b6f88252618e602110000000575e3f0e9000000000000000000

1 output(s) for total of 1.767689578000 dcy

stealth address amount amount idx
00: 78221215de5a8e3d4560becb8d3b106c59c14c289eb9ff0d806ebd4f095ffa09 1.767689578000 1215823 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": 766770, "vin": [ { "gen": { "height": 766760 } } ], "vout": [ { "amount": 1767689578, "target": { "key": "78221215de5a8e3d4560becb8d3b106c59c14c289eb9ff0d806ebd4f095ffa09" } } ], "extra": [ 1, 44, 189, 130, 45, 112, 149, 227, 107, 68, 69, 10, 125, 208, 45, 35, 30, 177, 68, 32, 33, 201, 120, 217, 172, 193, 43, 111, 136, 37, 38, 24, 230, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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