Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23a07149c0edae6afa9c6ba72716c63521b5c41ebc831db3495e90fedc65749a

Tx prefix hash: 15809b1c8d01b1f0f2c4fd583c4e8dc302757c88651c7889e9e0fe7e5c9650c3
Tx public key: f93f8808c6ff0200ac411e522d09b76c3232e0e6223d1b7f4070e35520f7f234
Timestamp: 1582438465 Timestamp [UCT]: 2020-02-23 06:14:25 Age [y:d:h:m:s]: 04:352:15:42:12
Block: 70713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144362 RingCT/type: yes/0
Extra: 01f93f8808c6ff0200ac411e522d09b76c3232e0e6223d1b7f4070e35520f7f23402110000000156c366d3000000000000000000

1 output(s) for total of 357.848564401000 dcy

stealth address amount amount idx
00: 8128553b94b9209e40247ffa7210e24a34f2ed8a2238a0bf4a7c9ff1afe90e4a 357.848564401000 130651 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": 70723, "vin": [ { "gen": { "height": 70713 } } ], "vout": [ { "amount": 357848564401, "target": { "key": "8128553b94b9209e40247ffa7210e24a34f2ed8a2238a0bf4a7c9ff1afe90e4a" } } ], "extra": [ 1, 249, 63, 136, 8, 198, 255, 2, 0, 172, 65, 30, 82, 45, 9, 183, 108, 50, 50, 224, 230, 34, 61, 27, 127, 64, 112, 227, 85, 32, 247, 242, 52, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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