Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dfd437a26a55311f37efb39838a62df563365b788a0a29d6cc3fca9ce429185

Tx prefix hash: 97fb904b8ad4bd016132d879b03f00038e91dffd997bf71f8943f525dc360e8a
Tx public key: 25fdfb9b255847714b628400074160d6d7ac31d2640577607df13c43609c80e3
Timestamp: 1577649345 Timestamp [UCT]: 2019-12-29 19:55:45 Age [y:d:h:m:s]: 05:148:04:15:34
Block: 34524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1255723 RingCT/type: yes/0
Extra: 0125fdfb9b255847714b628400074160d6d7ac31d2640577607df13c43609c80e30211000000214ac5aa02000000000000000000

1 output(s) for total of 471.637699189000 dcy

stealth address amount amount idx
00: 9a3adf3fed2339587be9ac71b4f562d8d5068acdc5714c90caae0fe1926213c4 471.637699189000 58112 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": 34534, "vin": [ { "gen": { "height": 34524 } } ], "vout": [ { "amount": 471637699189, "target": { "key": "9a3adf3fed2339587be9ac71b4f562d8d5068acdc5714c90caae0fe1926213c4" } } ], "extra": [ 1, 37, 253, 251, 155, 37, 88, 71, 113, 75, 98, 132, 0, 7, 65, 96, 214, 215, 172, 49, 210, 100, 5, 119, 96, 125, 241, 60, 67, 96, 156, 128, 227, 2, 17, 0, 0, 0, 33, 74, 197, 170, 2, 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