Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd4bf2a422b54294f824e16aa87a71cc10074f0a9dda42dc26cfc23b8fb4122f

Tx prefix hash: 6ab31fd81896c4a0db0f45fe865569879bac040db59d421e10797dc92edba746
Tx public key: 4c4064af23196f5324256fe613aa2ab263e090c0ce662161d9d1b5b8e2e754a3
Timestamp: 1708730448 Timestamp [UCT]: 2024-02-23 23:20:48 Age [y:d:h:m:s]: 01:114:22:04:00
Block: 964127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343078 RingCT/type: yes/0
Extra: 014c4064af23196f5324256fe613aa2ab263e090c0ce662161d9d1b5b8e2e754a302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b67f0ebb9851dee6866730301e4d8ef008d6ea87d6ad93b4ea966843f69aab0a 0.600000000000 1423854 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": 964137, "vin": [ { "gen": { "height": 964127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b67f0ebb9851dee6866730301e4d8ef008d6ea87d6ad93b4ea966843f69aab0a" } } ], "extra": [ 1, 76, 64, 100, 175, 35, 25, 111, 83, 36, 37, 111, 230, 19, 170, 42, 178, 99, 224, 144, 192, 206, 102, 33, 97, 217, 209, 181, 184, 226, 231, 84, 163, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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