Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c53cb902b10b9de90173da76630aad0562e2fab30b43180f34f92dd6707d16e

Tx prefix hash: a527f214ea73096e25015b31301eb6e30329d1630d7f05e5ecc3f4326dd92fac
Tx public key: c7ff9ab38077994609e501bebcf0ffdb2e37f7756f67eacc846d3b203df53e83
Timestamp: 1708339472 Timestamp [UCT]: 2024-02-19 10:44:32 Age [y:d:h:m:s]: 01:066:09:07:54
Block: 960881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308490 RingCT/type: yes/0
Extra: 01c7ff9ab38077994609e501bebcf0ffdb2e37f7756f67eacc846d3b203df53e8302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06d71724b026812b6c862d5c3dd61d03f61a345d4f33c0b9461fa0eae4a7f801 0.600000000000 1420468 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": 960891, "vin": [ { "gen": { "height": 960881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06d71724b026812b6c862d5c3dd61d03f61a345d4f33c0b9461fa0eae4a7f801" } } ], "extra": [ 1, 199, 255, 154, 179, 128, 119, 153, 70, 9, 229, 1, 190, 188, 240, 255, 219, 46, 55, 247, 117, 111, 103, 234, 204, 132, 109, 59, 32, 61, 245, 62, 131, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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