Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9229c4bd6898426d288c153f8116fb25d9cc98c910bee447dad6fec0a2a9811c

Tx prefix hash: 2457565672a5dc0e72ae0d5295eb176345289536bfd57d4b0a32e10b5cd6c127
Tx public key: ac9f8435750703ad291fdf60f514cb517fe36e7a2c61ae946f8c51ddf0eabf0c
Timestamp: 1699400124 Timestamp [UCT]: 2023-11-07 23:35:24 Age [y:d:h:m:s]: 02:062:20:15:45
Block: 886776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 564779 RingCT/type: yes/0
Extra: 01ac9f8435750703ad291fdf60f514cb517fe36e7a2c61ae946f8c51ddf0eabf0c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.707526966000 dcy

stealth address amount amount idx
00: 425a56a7590f6a3fa2c5a7a83d70b92eac0c11c298e313488f6c685403f742ae 0.707526966000 1342619 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": 886786, "vin": [ { "gen": { "height": 886776 } } ], "vout": [ { "amount": 707526966, "target": { "key": "425a56a7590f6a3fa2c5a7a83d70b92eac0c11c298e313488f6c685403f742ae" } } ], "extra": [ 1, 172, 159, 132, 53, 117, 7, 3, 173, 41, 31, 223, 96, 245, 20, 203, 81, 127, 227, 110, 122, 44, 97, 174, 148, 111, 140, 81, 221, 240, 234, 191, 12, 2, 17, 0, 0, 0, 1, 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