Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c9be9e1e3b1b374236cf60783d90f6867722a57eaaf1ba863539c72f4ca742b

Tx prefix hash: a37bc7658e580e09a62a1b7e941e3909c31480353b1ed75a41ce5a3207547741
Tx public key: fe096a69559ea5b3f9c48c472f0146520bfa8763e9868a7b96c919efa75abf41
Timestamp: 1577697219 Timestamp [UCT]: 2019-12-30 09:13:39 Age [y:d:h:m:s]: 05:306:20:48:21
Block: 34904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366833 RingCT/type: yes/0
Extra: 01fe096a69559ea5b3f9c48c472f0146520bfa8763e9868a7b96c919efa75abf410211000000028a2ee0d9000000000000000000

1 output(s) for total of 470.272316344000 dcy

stealth address amount amount idx
00: a54056594e8c51d21dd922db483340fb109cd707eee7fed7641db016c6d90749 470.272316344000 58807 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": 34914, "vin": [ { "gen": { "height": 34904 } } ], "vout": [ { "amount": 470272316344, "target": { "key": "a54056594e8c51d21dd922db483340fb109cd707eee7fed7641db016c6d90749" } } ], "extra": [ 1, 254, 9, 106, 105, 85, 158, 165, 179, 249, 196, 140, 71, 47, 1, 70, 82, 11, 250, 135, 99, 233, 134, 138, 123, 150, 201, 25, 239, 167, 90, 191, 65, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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