Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6aee98714082490ec958e7f840d4780efac4b99cc1813b76137049a2a840c24

Tx prefix hash: 942303cd6811a5cb97669e81f9ab574d304e2dd39bfa8fe62f9bac3af349d351
Tx public key: d1efab43bdf2912e532a56145700e1df6a9fa441d193d8eeaedab7c7783d30a6
Timestamp: 1682523029 Timestamp [UCT]: 2023-04-26 15:30:29 Age [y:d:h:m:s]: 02:039:14:30:04
Block: 747103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550477 RingCT/type: yes/0
Extra: 01d1efab43bdf2912e532a56145700e1df6a9fa441d193d8eeaedab7c7783d30a6021100000002b3164c24000000000000000000

1 output(s) for total of 2.053703916000 dcy

stealth address amount amount idx
00: 19f3e58a221d024ff20ad13be8e5d38ae7dd8b83ad2242b29fba4b455acfe5d7 2.053703916000 1194740 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": 747113, "vin": [ { "gen": { "height": 747103 } } ], "vout": [ { "amount": 2053703916, "target": { "key": "19f3e58a221d024ff20ad13be8e5d38ae7dd8b83ad2242b29fba4b455acfe5d7" } } ], "extra": [ 1, 209, 239, 171, 67, 189, 242, 145, 46, 83, 42, 86, 20, 87, 0, 225, 223, 106, 159, 164, 65, 209, 147, 216, 238, 174, 218, 183, 199, 120, 61, 48, 166, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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