Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79084f454d5b848ec16b51706934f6bb50a7ce55cb7321dbfbb9c697c509fe6e

Tx prefix hash: 663e79811b9cc0d73df03a95c6c9042fb8b477babf02e79895184546698fe598
Tx public key: b24708c555c80dd49949cdb3b87ed065a90010f8ec22aff7b141e6ccd5e6c034
Timestamp: 1699602091 Timestamp [UCT]: 2023-11-10 07:41:31 Age [y:d:h:m:s]: 01:108:04:30:40
Block: 888459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338463 RingCT/type: yes/0
Extra: 01b24708c555c80dd49949cdb3b87ed065a90010f8ec22aff7b141e6ccd5e6c03402110000000175e3f0e9000000000000000000

1 output(s) for total of 0.698500170000 dcy

stealth address amount amount idx
00: efa0a9d03c4edf4379bea9c257124d8ad5175fdb1cb3d51c2857872cf5c29952 0.698500170000 1344400 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": 888469, "vin": [ { "gen": { "height": 888459 } } ], "vout": [ { "amount": 698500170, "target": { "key": "efa0a9d03c4edf4379bea9c257124d8ad5175fdb1cb3d51c2857872cf5c29952" } } ], "extra": [ 1, 178, 71, 8, 197, 85, 200, 13, 212, 153, 73, 205, 179, 184, 126, 208, 101, 169, 0, 16, 248, 236, 34, 175, 247, 177, 65, 230, 204, 213, 230, 192, 52, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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