Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 110ea54bebcc24a41cf4c4167672b1af4cb6fdcdfac85e1eaae80bc7f5674edd

Tx prefix hash: bf527de7c898dd82ea9e7702b317521af228967877d34bd9885e1fc46df19ae3
Tx public key: 496e587cf5f5002bd267e2cc019348b778166df05f620e351c45c843abb7cddf
Timestamp: 1583753264 Timestamp [UCT]: 2020-03-09 11:27:44 Age [y:d:h:m:s]: 04:261:17:09:40
Block: 79424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1081736 RingCT/type: yes/0
Extra: 01496e587cf5f5002bd267e2cc019348b778166df05f620e351c45c843abb7cddf0211000000526d997e00000000000000000000

1 output(s) for total of 334.839055578000 dcy

stealth address amount amount idx
00: 1001baae91f3afc2ee53a62c5a96a346a4b34c239ad159705ec8baf26b6b05bf 334.839055578000 145260 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": 79434, "vin": [ { "gen": { "height": 79424 } } ], "vout": [ { "amount": 334839055578, "target": { "key": "1001baae91f3afc2ee53a62c5a96a346a4b34c239ad159705ec8baf26b6b05bf" } } ], "extra": [ 1, 73, 110, 88, 124, 245, 245, 0, 43, 210, 103, 226, 204, 1, 147, 72, 183, 120, 22, 109, 240, 95, 98, 14, 53, 28, 69, 200, 67, 171, 183, 205, 223, 2, 17, 0, 0, 0, 82, 109, 153, 126, 0, 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