Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75242195a4633b0d6ff1623aaab4993d43ae74d21a686d6ab6dea6171fde3a8

Tx prefix hash: f5f5935bf754caff38cc8e2ed6adeb2906783f04808e7059032ae41b8fe2244a
Tx public key: 285a26e2341282ee9aa0f078e3876e4dd301b0c9017b38e94b799047b34fa6d6
Timestamp: 1707573810 Timestamp [UCT]: 2024-02-10 14:03:30 Age [y:d:h:m:s]: 01:269:11:47:23
Block: 954527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 451354 RingCT/type: yes/0
Extra: 01285a26e2341282ee9aa0f078e3876e4dd301b0c9017b38e94b799047b34fa6d60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 218ab66947dfec58c417f24bc26f54a143bfdc3be6199f2e63a986a4a291a68e 0.600000000000 1413807 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": 954537, "vin": [ { "gen": { "height": 954527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "218ab66947dfec58c417f24bc26f54a143bfdc3be6199f2e63a986a4a291a68e" } } ], "extra": [ 1, 40, 90, 38, 226, 52, 18, 130, 238, 154, 160, 240, 120, 227, 135, 110, 77, 211, 1, 176, 201, 1, 123, 56, 233, 75, 121, 144, 71, 179, 79, 166, 214, 2, 17, 0, 0, 0, 5, 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