Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffcd033690e832282ace915568406ee5708cb28ea1f05e03cf32eaf123ef870

Tx prefix hash: 38dae423dc8a3c01e9bbdf971d1d6bb46c7f6e69fcdc1fbc13261645bd996638
Tx public key: ff7e18960def6a6b758ad1edf5433788b921e92a98ff65df82f47b9ded9a3b5e
Timestamp: 1716766294 Timestamp [UCT]: 2024-05-26 23:31:34 Age [y:d:h:m:s]: 00:296:11:03:02
Block: 1030753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211891 RingCT/type: yes/0
Extra: 01ff7e18960def6a6b758ad1edf5433788b921e92a98ff65df82f47b9ded9a3b5e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74859d20d102f1d1c0ff4450a6aab59703ef977b3249cb34f0f9833f55666874 0.600000000000 1499034 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": 1030763, "vin": [ { "gen": { "height": 1030753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74859d20d102f1d1c0ff4450a6aab59703ef977b3249cb34f0f9833f55666874" } } ], "extra": [ 1, 255, 126, 24, 150, 13, 239, 106, 107, 117, 138, 209, 237, 245, 67, 55, 136, 185, 33, 233, 42, 152, 255, 101, 223, 130, 244, 123, 157, 237, 154, 59, 94, 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