Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2355a3f0f3c0ad9bc3e34e8b7344ccfa2b9b5f360ebc9efea0c0fb53e31c3026

Tx prefix hash: 4f06088022aae39b4b0404a1f0cf65ab52e1f648268ee230f510a06db6ac23e8
Tx public key: 334e987262b080519503884f76422b36de7aa1ade93b2de90c1615905ebb52f4
Timestamp: 1582894363 Timestamp [UCT]: 2020-02-28 12:52:43 Age [y:d:h:m:s]: 05:005:20:51:08
Block: 73368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158501 RingCT/type: yes/0
Extra: 01334e987262b080519503884f76422b36de7aa1ade93b2de90c1615905ebb52f40211000000027adf42d3000000000000000000

1 output(s) for total of 350.672863063000 dcy

stealth address amount amount idx
00: 67d477ab5ae39e212dd6e9d24fb927a9ba73dc2328f5ccb5a912dbec069b119e 350.672863063000 135345 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": 73378, "vin": [ { "gen": { "height": 73368 } } ], "vout": [ { "amount": 350672863063, "target": { "key": "67d477ab5ae39e212dd6e9d24fb927a9ba73dc2328f5ccb5a912dbec069b119e" } } ], "extra": [ 1, 51, 78, 152, 114, 98, 176, 128, 81, 149, 3, 136, 79, 118, 66, 43, 54, 222, 122, 161, 173, 233, 59, 45, 233, 12, 22, 21, 144, 94, 187, 82, 244, 2, 17, 0, 0, 0, 2, 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