Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de82896a9665ecff0b6c79baa07285c4864bee7ebc83385954caa8b00a21fd8

Tx prefix hash: ddbb9c02b2bf125020166865f7c72da5ec189fb2bff3db5aa77fad27c7b59901
Tx public key: 79b4aa06682b4f0142d623d720782284db48632a7ca436a0a0b46b94961d93c8
Timestamp: 1728553078 Timestamp [UCT]: 2024-10-10 09:37:58 Age [y:d:h:m:s]: 00:174:00:46:32
Block: 1128465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124165 RingCT/type: yes/0
Extra: 0179b4aa06682b4f0142d623d720782284db48632a7ca436a0a0b46b94961d93c8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd5d47b416272b7c0c83de7bed1c661c0ae7873347f506e26267af51ac9e1dc0 0.600000000000 1611284 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": 1128475, "vin": [ { "gen": { "height": 1128465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd5d47b416272b7c0c83de7bed1c661c0ae7873347f506e26267af51ac9e1dc0" } } ], "extra": [ 1, 121, 180, 170, 6, 104, 43, 79, 1, 66, 214, 35, 215, 32, 120, 34, 132, 219, 72, 99, 42, 124, 164, 54, 160, 160, 180, 107, 148, 150, 29, 147, 200, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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