Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 041ec90bad76b1eff3b8c84a0f6de59582f6af003d0cd0060f0600b047cc2f30

Tx prefix hash: d19105d551b83b4ccebc6f40a3cf816a52dbccd1a6bacd56fe3090c566d6847e
Tx public key: 206acba9d9d75e7e617a6cf3d58105effdcc59d3db7fab40d987bb5887c1ab70
Timestamp: 1708100911 Timestamp [UCT]: 2024-02-16 16:28:31 Age [y:d:h:m:s]: 01:038:20:44:45
Block: 958904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288795 RingCT/type: yes/0
Extra: 01206acba9d9d75e7e617a6cf3d58105effdcc59d3db7fab40d987bb5887c1ab700211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb90f08e32f191ef3f34dbbc4b6c4392c0a5f3842845371fe4376bd0c8bd439e 0.600000000000 1418375 of 15

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": 958914, "vin": [ { "gen": { "height": 958904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb90f08e32f191ef3f34dbbc4b6c4392c0a5f3842845371fe4376bd0c8bd439e" } } ], "extra": [ 1, 32, 106, 203, 169, 217, 215, 94, 126, 97, 122, 108, 243, 213, 129, 5, 239, 253, 204, 89, 211, 219, 127, 171, 64, 217, 135, 187, 88, 135, 193, 171, 112, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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