Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d86ca86e97e8bf52778d352af264c8bdd6646504b50bd4b72e942f74aed58a5

Tx prefix hash: c68ac88b41088000a7aea974f60f6e539d188b5f7931980cadfd66141062f82c
Tx public key: 917eccfdb56e357a7203fd75e1fce20b02954bb5b5a45e7b5ab85500cb3170dc
Timestamp: 1712240657 Timestamp [UCT]: 2024-04-04 14:24:17 Age [y:d:h:m:s]: 01:244:02:28:43
Block: 993199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433220 RingCT/type: yes/0
Extra: 01917eccfdb56e357a7203fd75e1fce20b02954bb5b5a45e7b5ab85500cb3170dc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26b91466054769f30df4fd1ecb233b26056285ec6a7c462eb8afb5e3e78ebf38 0.600000000000 1453581 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": 993209, "vin": [ { "gen": { "height": 993199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26b91466054769f30df4fd1ecb233b26056285ec6a7c462eb8afb5e3e78ebf38" } } ], "extra": [ 1, 145, 126, 204, 253, 181, 110, 53, 122, 114, 3, 253, 117, 225, 252, 226, 11, 2, 149, 75, 181, 181, 164, 94, 123, 90, 184, 85, 0, 203, 49, 112, 220, 2, 17, 0, 0, 0, 2, 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