Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99bbfd54be5abe7284f803f6870f1b8e3ab16837f0c8a518c1f0790cd1dc73e1

Tx prefix hash: 64a2179ad34b65a86b0d076b368bb3ae7d0341ab026a2833bbc2d03dd399f577
Tx public key: 70ebb22cef98df3f332c92aefa013abcf6588fb3324c1d7ac799aad8b10a775a
Timestamp: 1717608403 Timestamp [UCT]: 2024-06-05 17:26:43 Age [y:d:h:m:s]: 01:157:22:08:32
Block: 1037734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371443 RingCT/type: yes/0
Extra: 0170ebb22cef98df3f332c92aefa013abcf6588fb3324c1d7ac799aad8b10a775a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23677e05b32d5412de4b15011b09edcb7ddad722dda8c5d3e6695c3bcf4790fa 0.600000000000 1506289 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": 1037744, "vin": [ { "gen": { "height": 1037734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23677e05b32d5412de4b15011b09edcb7ddad722dda8c5d3e6695c3bcf4790fa" } } ], "extra": [ 1, 112, 235, 178, 44, 239, 152, 223, 63, 51, 44, 146, 174, 250, 1, 58, 188, 246, 88, 143, 179, 50, 76, 29, 122, 199, 153, 170, 216, 177, 10, 119, 90, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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