Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af63f4f9e13d9fe3f15cfdaa110232eb6034376a287ff0707a38dacaa73d9cbc

Tx prefix hash: aa0c5b364fc04d55f9a56bebe9f4c4b794f4f0a778b4208722be0cbca3fd3912
Tx public key: 68e71e27d43ef9476d1225231feefc3282e94c53f84ba3d96df903b0a634b4c5
Timestamp: 1720727012 Timestamp [UCT]: 2024-07-11 19:43:32 Age [y:d:h:m:s]: 00:248:15:48:00
Block: 1063589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177659 RingCT/type: yes/0
Extra: 0168e71e27d43ef9476d1225231feefc3282e94c53f84ba3d96df903b0a634b4c502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8f1a4676d03286aeb5608ba70d51a9d050a149cffeb3653791bd7a63c83866a 0.600000000000 1534106 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": 1063599, "vin": [ { "gen": { "height": 1063589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8f1a4676d03286aeb5608ba70d51a9d050a149cffeb3653791bd7a63c83866a" } } ], "extra": [ 1, 104, 231, 30, 39, 212, 62, 249, 71, 109, 18, 37, 35, 31, 238, 252, 50, 130, 233, 76, 83, 248, 75, 163, 217, 109, 249, 3, 176, 166, 52, 180, 197, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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