Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9ecd33121f23990832ebcebaedab13b2d94cd1b9e2b3c109a94853efa617391

Tx prefix hash: 0be7b1eee9234dc340e62c361ed75cdf3d1045caa10134cb464dba27bbf91978
Tx public key: d061abc98f7d0b95c0fc202d2ab652155cbea225d7a57012aa3cdb1ae4f66fb1
Timestamp: 1710724423 Timestamp [UCT]: 2024-03-18 01:13:43 Age [y:d:h:m:s]: 00:255:13:24:46
Block: 980675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182946 RingCT/type: yes/0
Extra: 01d061abc98f7d0b95c0fc202d2ab652155cbea225d7a57012aa3cdb1ae4f66fb102110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcf7bd9230ac5b90195da1d55afa2137169e49d106cc31b91445303ccf98ff1c 0.600000000000 1440756 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": 980685, "vin": [ { "gen": { "height": 980675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcf7bd9230ac5b90195da1d55afa2137169e49d106cc31b91445303ccf98ff1c" } } ], "extra": [ 1, 208, 97, 171, 201, 143, 125, 11, 149, 192, 252, 32, 45, 42, 182, 82, 21, 92, 190, 162, 37, 215, 165, 112, 18, 170, 60, 219, 26, 228, 246, 111, 177, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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