Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde03a811fd1bede1b1319d808057691fc030e667937c01f096eabe0563219e5

Tx prefix hash: 5493ae2f0b05d8fd557d9b0649f1ff259ed7f01cfa64d3fff31cec01ed5fee88
Tx public key: 56c3780be6aed1218b2c0303259761256715e9e0c0e6764a4b64d63180cb3aaa
Timestamp: 1738351722 Timestamp [UCT]: 2025-01-31 19:28:42 Age [y:d:h:m:s]: 00:294:04:52:53
Block: 1209279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208026 RingCT/type: yes/0
Extra: 0156c3780be6aed1218b2c0303259761256715e9e0c0e6764a4b64d63180cb3aaa0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c633be565bac8a5b7d3c9d2e0a454e7faf4f1a1ce0cd543eaac8cd46e0a10825 0.600000000000 1696020 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": 1209289, "vin": [ { "gen": { "height": 1209279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c633be565bac8a5b7d3c9d2e0a454e7faf4f1a1ce0cd543eaac8cd46e0a10825" } } ], "extra": [ 1, 86, 195, 120, 11, 230, 174, 209, 33, 139, 44, 3, 3, 37, 151, 97, 37, 103, 21, 233, 224, 192, 230, 118, 74, 75, 100, 214, 49, 128, 203, 58, 170, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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