Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504715cc17c7087d3f5b02336d1eab2b609f7a4a5ac806a63b5ba0504e0372ea

Tx prefix hash: 645c1c690974300f352e96aad4421689bd97802e7a3480a71d9ae4aabc835bb4
Tx public key: 74106fa6b52eb1e934acf1436d9fc71458fb300ed5002215d615f49d4f9bc425
Timestamp: 1619711364 Timestamp [UCT]: 2021-04-29 15:49:24 Age [y:d:h:m:s]: 04:035:23:16:35
Block: 250358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1046776 RingCT/type: yes/0
Extra: 0174106fa6b52eb1e934acf1436d9fc71458fb300ed5002215d615f49d4f9bc4250211000000010dc70aa7000000000000000000

1 output(s) for total of 90.879949896000 dcy

stealth address amount amount idx
00: c7019850a61381594721d0cda7fdd6ad7ccf03384ee007724984e1c8714d06ee 90.879949896000 524804 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": 250368, "vin": [ { "gen": { "height": 250358 } } ], "vout": [ { "amount": 90879949896, "target": { "key": "c7019850a61381594721d0cda7fdd6ad7ccf03384ee007724984e1c8714d06ee" } } ], "extra": [ 1, 116, 16, 111, 166, 181, 46, 177, 233, 52, 172, 241, 67, 109, 159, 199, 20, 88, 251, 48, 14, 213, 0, 34, 21, 214, 21, 244, 157, 79, 155, 196, 37, 2, 17, 0, 0, 0, 1, 13, 199, 10, 167, 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