Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ff744076f945b4aec01705e4ae881465bfa93664951c6e2954927acd8db4c1e

Tx prefix hash: d549ed1ce275d6b9d234fef13aa6f754dce3fdcb2b6463f9be6b4e6af462c402
Tx public key: 8bc2629fb9e8774ed1766a41daa2bdd8e122310143199f1bea612f283654283b
Timestamp: 1703445026 Timestamp [UCT]: 2023-12-24 19:10:26 Age [y:d:h:m:s]: 01:324:19:37:08
Block: 920312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490982 RingCT/type: yes/0
Extra: 018bc2629fb9e8774ed1766a41daa2bdd8e122310143199f1bea612f283654283b021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ccc603fc4c10d58dd37cdf68caca1490d24e7a7bcf119fb98332f00baacbc8 0.600000000000 1377990 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": 920322, "vin": [ { "gen": { "height": 920312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ccc603fc4c10d58dd37cdf68caca1490d24e7a7bcf119fb98332f00baacbc8" } } ], "extra": [ 1, 139, 194, 98, 159, 185, 232, 119, 78, 209, 118, 106, 65, 218, 162, 189, 216, 225, 34, 49, 1, 67, 25, 159, 27, 234, 97, 47, 40, 54, 84, 40, 59, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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