Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34de8cf3b37eaa9eeead8cb70118fd3dc0e9fdb491e1b6848d0dc4b3b8500f5b

Tx prefix hash: 68ed444b8a0aa16e946f08bd427b0e3c26c5af0f8b68fb5b479bed4dfb9c943d
Tx public key: 70938e81136531dc313185e9098bce80f837fdc0473fd15085adfbbb936dd8e2
Timestamp: 1722049435 Timestamp [UCT]: 2024-07-27 03:03:55 Age [y:d:h:m:s]: 00:051:16:43:41
Block: 1074542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37034 RingCT/type: yes/0
Extra: 0170938e81136531dc313185e9098bce80f837fdc0473fd15085adfbbb936dd8e2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71dadbafff33b6c0358ba38acd057379c4a7fd3c0773b9f94272b8c92eeb01ed 0.600000000000 1547055 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": 1074552, "vin": [ { "gen": { "height": 1074542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71dadbafff33b6c0358ba38acd057379c4a7fd3c0773b9f94272b8c92eeb01ed" } } ], "extra": [ 1, 112, 147, 142, 129, 19, 101, 49, 220, 49, 49, 133, 233, 9, 139, 206, 128, 248, 55, 253, 192, 71, 63, 209, 80, 133, 173, 251, 187, 147, 109, 216, 226, 2, 17, 0, 0, 0, 7, 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