Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264f0cc500ae08080e4ea91953a31e161fc8f22f1e0b3e7b447c3bb036abc2ad

Tx prefix hash: 728dd155cb85896d881272fbb43975d187ce76d014990e6133418e187d090644
Tx public key: 7b6814d3edf946c795fc1b049c88dd49764a16d1b10a1d4fc9d17dde5a295af9
Timestamp: 1720660948 Timestamp [UCT]: 2024-07-11 01:22:28 Age [y:d:h:m:s]: 00:296:02:46:58
Block: 1063040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211572 RingCT/type: yes/0
Extra: 017b6814d3edf946c795fc1b049c88dd49764a16d1b10a1d4fc9d17dde5a295af9021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebf291accda369f794e4763b1a259d717e801176182a2076e237ad6002816daf 0.600000000000 1533553 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": 1063050, "vin": [ { "gen": { "height": 1063040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebf291accda369f794e4763b1a259d717e801176182a2076e237ad6002816daf" } } ], "extra": [ 1, 123, 104, 20, 211, 237, 249, 70, 199, 149, 252, 27, 4, 156, 136, 221, 73, 118, 74, 22, 209, 177, 10, 29, 79, 201, 209, 125, 222, 90, 41, 90, 249, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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