Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e074d61df0a1ab14c1749ec6248615d66cc37af725ef5e93613f4e79ed3cef6

Tx prefix hash: 05e9fda660901db88209bb9fe0a8ba56cd570e957414cbfa626f60ac17fe719e
Tx public key: 8516ddf5759a46869f9d52b2b6fbd1edd621756bfc87a0da65f2f01a6c02e7c5
Timestamp: 1707817576 Timestamp [UCT]: 2024-02-13 09:46:16 Age [y:d:h:m:s]: 01:053:11:02:17
Block: 956555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299232 RingCT/type: yes/0
Extra: 018516ddf5759a46869f9d52b2b6fbd1edd621756bfc87a0da65f2f01a6c02e7c50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8837e9b2f0d3b702edb89bbee7f0d01740374ebcb56b738c1afd386075371d82 0.600000000000 1415863 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": 956565, "vin": [ { "gen": { "height": 956555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8837e9b2f0d3b702edb89bbee7f0d01740374ebcb56b738c1afd386075371d82" } } ], "extra": [ 1, 133, 22, 221, 245, 117, 154, 70, 134, 159, 157, 82, 178, 182, 251, 209, 237, 214, 33, 117, 107, 252, 135, 160, 218, 101, 242, 240, 26, 108, 2, 231, 197, 2, 17, 0, 0, 0, 6, 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