Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dffd8f3922cbead4b91d1666f542dae8cee3f63e5c5e051ef37c2f275eef83b

Tx prefix hash: 19eeb2edf03a964ff0c192d91bcf804adfebf0f4ef9e63a632729d75623bd5d9
Tx public key: bab0df002efc82cdd499ec01f948a4794cc866e5098b7cc3aca086f3c6645674
Timestamp: 1703971684 Timestamp [UCT]: 2023-12-30 21:28:04 Age [y:d:h:m:s]: 01:311:19:15:26
Block: 924662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481667 RingCT/type: yes/0
Extra: 01bab0df002efc82cdd499ec01f948a4794cc866e5098b7cc3aca086f3c66456740211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68b5ad71c3996ba378a51579c7f42f0ad87a03c8a5e6bdd2b3c727957bbcd240 0.600000000000 1382418 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": 924672, "vin": [ { "gen": { "height": 924662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68b5ad71c3996ba378a51579c7f42f0ad87a03c8a5e6bdd2b3c727957bbcd240" } } ], "extra": [ 1, 186, 176, 223, 0, 46, 252, 130, 205, 212, 153, 236, 1, 249, 72, 164, 121, 76, 200, 102, 229, 9, 139, 124, 195, 172, 160, 134, 243, 198, 100, 86, 116, 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