Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19ef2fa1007b1a5a34cf405a6561efdb14e9dbb20cd10fd6e7be01b784ed797c

Tx prefix hash: 3b65e7b9b625310dc2346b9fb188f10437280247cc26ed7351c78be6fdf31190
Tx public key: 46bdc3d6c54b32601cdf226b0fd9f9b102104841e855996f384fbc76b1113304
Timestamp: 1581360626 Timestamp [UCT]: 2020-02-10 18:50:26 Age [y:d:h:m:s]: 05:067:01:57:28
Block: 62155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1200796 RingCT/type: yes/0
Extra: 0146bdc3d6c54b32601cdf226b0fd9f9b102104841e855996f384fbc76b111330402110000008a12c4732d000000000000000000

1 output(s) for total of 381.993082541000 dcy

stealth address amount amount idx
00: dc76f079c6359bfc51be0fd53092aa1010db18257835fda2429555e8940ce8e6 381.993082541000 114651 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": 62165, "vin": [ { "gen": { "height": 62155 } } ], "vout": [ { "amount": 381993082541, "target": { "key": "dc76f079c6359bfc51be0fd53092aa1010db18257835fda2429555e8940ce8e6" } } ], "extra": [ 1, 70, 189, 195, 214, 197, 75, 50, 96, 28, 223, 34, 107, 15, 217, 249, 177, 2, 16, 72, 65, 232, 85, 153, 111, 56, 79, 188, 118, 177, 17, 51, 4, 2, 17, 0, 0, 0, 138, 18, 196, 115, 45, 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