Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 661319d200207d1650e7ecd346ede08be422f487fac5086db070b1290c75c494

Tx prefix hash: 241177973b7a14b265175c269407045dea2a68232f2113f10c963e0390d07a91
Tx public key: 95a4cd9aa16d892511458d5398b2c576d5ffc96fee44b6fa1d0f1e40e029b21e
Timestamp: 1708262615 Timestamp [UCT]: 2024-02-18 13:23:35 Age [y:d:h:m:s]: 01:095:10:04:24
Block: 960247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329259 RingCT/type: yes/0
Extra: 0195a4cd9aa16d892511458d5398b2c576d5ffc96fee44b6fa1d0f1e40e029b21e0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1836d8650950df5d52b62b6e27f505b23348cfafcf15e1ff7d83f3aa151cc327 0.600000000000 1419810 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": 960257, "vin": [ { "gen": { "height": 960247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1836d8650950df5d52b62b6e27f505b23348cfafcf15e1ff7d83f3aa151cc327" } } ], "extra": [ 1, 149, 164, 205, 154, 161, 109, 137, 37, 17, 69, 141, 83, 152, 178, 197, 118, 213, 255, 201, 111, 238, 68, 182, 250, 29, 15, 30, 64, 224, 41, 178, 30, 2, 17, 0, 0, 0, 5, 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