Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cae0771117daac9fd790097fc1e1183126245077762e72691f3b1b9c8908351

Tx prefix hash: 92b88f1172eb3954a1f77d2342c070fb1f2ee4c4521cf4723b77bbcd38802116
Tx public key: 4226d2e1c67af3db3c3c2988ae9f18421927279e418879f390b0c95dc96c801f
Timestamp: 1707760544 Timestamp [UCT]: 2024-02-12 17:55:44 Age [y:d:h:m:s]: 01:057:12:15:54
Block: 956080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302148 RingCT/type: yes/0
Extra: 014226d2e1c67af3db3c3c2988ae9f18421927279e418879f390b0c95dc96c801f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eabdd3dd26e341e71f9321501795d0761cc0daaaffe7155ce5402a552fd8f5e 0.600000000000 1415382 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": 956090, "vin": [ { "gen": { "height": 956080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eabdd3dd26e341e71f9321501795d0761cc0daaaffe7155ce5402a552fd8f5e" } } ], "extra": [ 1, 66, 38, 210, 225, 198, 122, 243, 219, 60, 60, 41, 136, 174, 159, 24, 66, 25, 39, 39, 158, 65, 136, 121, 243, 144, 176, 201, 93, 201, 108, 128, 31, 2, 17, 0, 0, 0, 5, 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