Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65e0b5cd73b03018c017e94a911c14eb02b94205ebd8c55326149550881a91d6

Tx prefix hash: 4e11b18470da91bfbf272a1710dd47bfa532c8fb396602e070f1af7b201132e0
Tx public key: 2f5b3a1c9a7686f688e0a62872aee87618766a502aa5d261d06e151c1f94cc98
Timestamp: 1649217550 Timestamp [UCT]: 2022-04-06 03:59:10 Age [y:d:h:m:s]: 03:020:10:11:25
Block: 474165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795041 RingCT/type: yes/0
Extra: 012f5b3a1c9a7686f688e0a62872aee87618766a502aa5d261d06e151c1f94cc98021100000017d3fcec30000000000000000000

1 output(s) for total of 16.477630623000 dcy

stealth address amount amount idx
00: 8c5a5e694d1f096366c3e9ff536ffb3bcb17aeb1fdbc35205af249686152d5c3 16.477630623000 894150 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": 474175, "vin": [ { "gen": { "height": 474165 } } ], "vout": [ { "amount": 16477630623, "target": { "key": "8c5a5e694d1f096366c3e9ff536ffb3bcb17aeb1fdbc35205af249686152d5c3" } } ], "extra": [ 1, 47, 91, 58, 28, 154, 118, 134, 246, 136, 224, 166, 40, 114, 174, 232, 118, 24, 118, 106, 80, 42, 165, 210, 97, 208, 110, 21, 28, 31, 148, 204, 152, 2, 17, 0, 0, 0, 23, 211, 252, 236, 48, 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