Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 859edcd558ba65515ea5c8bfffa9db94b5cb246246f4e69d1d4d2c974dd8d666

Tx prefix hash: b853962a5e67538a2e99c656e47ba3a557d749731d9fc3589e44ee3c8084dfd1
Tx public key: eed08f4e94f088eae837c55ba72f56a5e50f8e28fd2996cc80fbcbeddaf8ab81
Timestamp: 1714450211 Timestamp [UCT]: 2024-04-30 04:10:11 Age [y:d:h:m:s]: 00:344:23:19:42
Block: 1011542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246607 RingCT/type: yes/0
Extra: 01eed08f4e94f088eae837c55ba72f56a5e50f8e28fd2996cc80fbcbeddaf8ab810211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8999414403e06b37878da2a6e233e459c858c697fab2de368e41ab98d515396c 0.600000000000 1473800 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": 1011552, "vin": [ { "gen": { "height": 1011542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8999414403e06b37878da2a6e233e459c858c697fab2de368e41ab98d515396c" } } ], "extra": [ 1, 238, 208, 143, 78, 148, 240, 136, 234, 232, 55, 197, 91, 167, 47, 86, 165, 229, 15, 142, 40, 253, 41, 150, 204, 128, 251, 203, 237, 218, 248, 171, 129, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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