Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d50da53a9b30c6fb72a6ba9be0c85e14783b95076fd34413027dce6579b7096

Tx prefix hash: e82955300982d72732dff1a48217ac5e449905cfedd1f14b626fc8cb04d5603c
Tx public key: 3dd52beed9ae52c29449c9f8028e4057a349a9aa467bb0914e6bd0f46c301aa1
Timestamp: 1705587335 Timestamp [UCT]: 2024-01-18 14:15:35 Age [y:d:h:m:s]: 01:069:23:37:24
Block: 938051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311107 RingCT/type: yes/0
Extra: 013dd52beed9ae52c29449c9f8028e4057a349a9aa467bb0914e6bd0f46c301aa10211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9caf020b969bb277dd7c57ee91fdcd1eb64c1e24f5de5d9d0e49598fd22a319e 0.600000000000 1396115 of 15

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": 938061, "vin": [ { "gen": { "height": 938051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9caf020b969bb277dd7c57ee91fdcd1eb64c1e24f5de5d9d0e49598fd22a319e" } } ], "extra": [ 1, 61, 213, 43, 238, 217, 174, 82, 194, 148, 73, 201, 248, 2, 142, 64, 87, 163, 73, 169, 170, 70, 123, 176, 145, 78, 107, 208, 244, 108, 48, 26, 161, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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