Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdae079e5fdfd760c1aa2665a0b8ea727dc58054559ff9b4a2e66ffe10fc406

Tx prefix hash: 9261ac418173665e9ff66d3943358c600a0edaaab57ce689291fc873f8d06cea
Tx public key: e11f10da19726af632504542e88dbdc8f9dc21b99fa895d11c323216f332a272
Timestamp: 1583034649 Timestamp [UCT]: 2020-03-01 03:50:49 Age [y:d:h:m:s]: 04:299:23:01:03
Block: 74425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108167 RingCT/type: yes/0
Extra: 01e11f10da19726af632504542e88dbdc8f9dc21b99fa895d11c323216f332a2720211000000b7c71d3ff9000000000000000000

1 output(s) for total of 347.856303674000 dcy

stealth address amount amount idx
00: c2c349c38252fcc107ad869e21c43fdce4b8c3f9e4239db85b618aa5f933c4c5 347.856303674000 137737 of 0

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": 74435, "vin": [ { "gen": { "height": 74425 } } ], "vout": [ { "amount": 347856303674, "target": { "key": "c2c349c38252fcc107ad869e21c43fdce4b8c3f9e4239db85b618aa5f933c4c5" } } ], "extra": [ 1, 225, 31, 16, 218, 25, 114, 106, 246, 50, 80, 69, 66, 232, 141, 189, 200, 249, 220, 33, 185, 159, 168, 149, 209, 28, 50, 50, 22, 243, 50, 162, 114, 2, 17, 0, 0, 0, 183, 199, 29, 63, 249, 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