Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 429ade9b0d60421f59cbd6cc17d250253f4a5b9b2b8f3681c569ba771d366eca

Tx prefix hash: 8a81660de9352a5914eb5934ed571d556c56bba2642712bed9d6ec037e52a28b
Tx public key: 3bfd28e6c509a5775536cacf89bd0d88064cb20f27f08afc7a6333049ffb3b47
Timestamp: 1576617357 Timestamp [UCT]: 2019-12-17 21:15:57 Age [y:d:h:m:s]: 05:053:21:00:20
Block: 27983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186267 RingCT/type: yes/0
Extra: 013bfd28e6c509a5775536cacf89bd0d88064cb20f27f08afc7a6333049ffb3b470211000000164ac5aa02000000000000000000

1 output(s) for total of 495.771514517000 dcy

stealth address amount amount idx
00: 8cbf2b7b722abf759a49e235aa750a298d705c7e647f0c77d5c00a255ed92dad 495.771514517000 46409 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": 27993, "vin": [ { "gen": { "height": 27983 } } ], "vout": [ { "amount": 495771514517, "target": { "key": "8cbf2b7b722abf759a49e235aa750a298d705c7e647f0c77d5c00a255ed92dad" } } ], "extra": [ 1, 59, 253, 40, 230, 197, 9, 165, 119, 85, 54, 202, 207, 137, 189, 13, 136, 6, 76, 178, 15, 39, 240, 138, 252, 122, 99, 51, 4, 159, 251, 59, 71, 2, 17, 0, 0, 0, 22, 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