Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17e75a6798d3dae8e3928e04077f6967a54cf63caaeb446d017cccee4f73f38

Tx prefix hash: 5b4afa3b5b50121ee6d5478e3776c0008b56a6ccd56c9a0cdc69850ad8d4dd48
Tx public key: 14cee8eec8f1d16f8b3694fcec907b23f19ca60acf0c26ce94e9fca0e7b94063
Timestamp: 1580481469 Timestamp [UCT]: 2020-01-31 14:37:49 Age [y:d:h:m:s]: 04:332:03:30:01
Block: 55872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128582 RingCT/type: yes/0
Extra: 0114cee8eec8f1d16f8b3694fcec907b23f19ca60acf0c26ce94e9fca0e7b94063021100000001ff58ae94000000000000000000

1 output(s) for total of 400.750151132000 dcy

stealth address amount amount idx
00: a08e5bd0f0f61a36681835c9a8fcbf1e1f6f06e12f84f17d4e3651c13cc15179 400.750151132000 103066 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": 55882, "vin": [ { "gen": { "height": 55872 } } ], "vout": [ { "amount": 400750151132, "target": { "key": "a08e5bd0f0f61a36681835c9a8fcbf1e1f6f06e12f84f17d4e3651c13cc15179" } } ], "extra": [ 1, 20, 206, 232, 238, 200, 241, 209, 111, 139, 54, 148, 252, 236, 144, 123, 35, 241, 156, 166, 10, 207, 12, 38, 206, 148, 233, 252, 160, 231, 185, 64, 99, 2, 17, 0, 0, 0, 1, 255, 88, 174, 148, 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