Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cacf004e9efadbd1319a3e7247948c7300d2177b195e8489b7232e7f3b8d2315

Tx prefix hash: 73f3b818a4c3718c5b415a1f84cb388866ee7fd93153c5ca77e48eb53acf0c52
Tx public key: ce8e49cc17719b4ff94b686774b9e568c6ab6983383363b37d9b3f1eeb7427f0
Timestamp: 1697368124 Timestamp [UCT]: 2023-10-15 11:08:44 Age [y:d:h:m:s]: 01:099:02:52:03
Block: 870129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332049 RingCT/type: yes/0
Extra: 01ce8e49cc17719b4ff94b686774b9e568c6ab6983383363b37d9b3f1eeb7427f00211000000014b8f5122000000000000000000

1 output(s) for total of 0.803343793000 dcy

stealth address amount amount idx
00: 3706951b1cf0e084609088db9a3a510c274acc00395cb7294c739e075ed5590a 0.803343793000 1325002 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": 870139, "vin": [ { "gen": { "height": 870129 } } ], "vout": [ { "amount": 803343793, "target": { "key": "3706951b1cf0e084609088db9a3a510c274acc00395cb7294c739e075ed5590a" } } ], "extra": [ 1, 206, 142, 73, 204, 23, 113, 155, 79, 249, 75, 104, 103, 116, 185, 229, 104, 198, 171, 105, 131, 56, 51, 99, 179, 125, 155, 63, 30, 235, 116, 39, 240, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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