Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81ac32cc1d707bf35b34950ad4508f97778f75598f8af4d66db864a8c2ae5662

Tx prefix hash: 25e53bff7b9a876a9c85292b348457c36bd29e492b3c192e9d102c093fa6b2f5
Tx public key: ab844a7af89690a7558ffb1d63b8c346ed649e934e927f7af791d0cfa9db9c26
Timestamp: 1709378094 Timestamp [UCT]: 2024-03-02 11:14:54 Age [y:d:h:m:s]: 01:108:06:03:41
Block: 969502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338291 RingCT/type: yes/0
Extra: 01ab844a7af89690a7558ffb1d63b8c346ed649e934e927f7af791d0cfa9db9c260211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52bc5d7bb034553c709652e78df211d78bc7143e414223b499d3e5190adf68d1 0.600000000000 1429335 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": 969512, "vin": [ { "gen": { "height": 969502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52bc5d7bb034553c709652e78df211d78bc7143e414223b499d3e5190adf68d1" } } ], "extra": [ 1, 171, 132, 74, 122, 248, 150, 144, 167, 85, 143, 251, 29, 99, 184, 195, 70, 237, 100, 158, 147, 78, 146, 127, 122, 247, 145, 208, 207, 169, 219, 156, 38, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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