Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0344f337c7e5769a554cf13078a28325963a1d9cec9957eba70ad413e9c96f7

Tx prefix hash: f0e0beba57b721d14f61d75b61ba956d762b41f9f22825080d51243ffceba360
Tx public key: ca736284db5ff37490ae34cbc65604654f7abf5962397d6c5759aa9e40f8df92
Timestamp: 1713316825 Timestamp [UCT]: 2024-04-17 01:20:25 Age [y:d:h:m:s]: 00:157:21:43:05
Block: 1002132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113126 RingCT/type: yes/0
Extra: 01ca736284db5ff37490ae34cbc65604654f7abf5962397d6c5759aa9e40f8df920211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86d2c32546876c08d1cdd9e76c7a5cde09f253f2b5bd99a23aaf7ef31b86af03 0.600000000000 1462648 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": 1002142, "vin": [ { "gen": { "height": 1002132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86d2c32546876c08d1cdd9e76c7a5cde09f253f2b5bd99a23aaf7ef31b86af03" } } ], "extra": [ 1, 202, 115, 98, 132, 219, 95, 243, 116, 144, 174, 52, 203, 198, 86, 4, 101, 79, 122, 191, 89, 98, 57, 125, 108, 87, 89, 170, 158, 64, 248, 223, 146, 2, 17, 0, 0, 0, 2, 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