Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50721b33c2cb71e08e42709a3f64580b4c70f2785225b83cf7456526403b0507

Tx prefix hash: 8a9d51f0deeadf2fa6242605b06cbb87d23a0dc533168d71255648a30365af0c
Tx public key: c3707229ec30b9f49f9047592794d32b665f710eb176dbfae04d40db45f16e29
Timestamp: 1582098708 Timestamp [UCT]: 2020-02-19 07:51:48 Age [y:d:h:m:s]: 04:353:21:59:21
Block: 67938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145221 RingCT/type: yes/0
Extra: 01c3707229ec30b9f49f9047592794d32b665f710eb176dbfae04d40db45f16e290211000000037adf42d3000000000000000000

1 output(s) for total of 365.505578976000 dcy

stealth address amount amount idx
00: be4c93e039fa8ffaa4b4a2dbc539234e8e59c3e9d0e37a86088f7d3baa55b47c 365.505578976000 125162 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": 67948, "vin": [ { "gen": { "height": 67938 } } ], "vout": [ { "amount": 365505578976, "target": { "key": "be4c93e039fa8ffaa4b4a2dbc539234e8e59c3e9d0e37a86088f7d3baa55b47c" } } ], "extra": [ 1, 195, 112, 114, 41, 236, 48, 185, 244, 159, 144, 71, 89, 39, 148, 211, 43, 102, 95, 113, 14, 177, 118, 219, 250, 224, 77, 64, 219, 69, 241, 110, 41, 2, 17, 0, 0, 0, 3, 122, 223, 66, 211, 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