Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f943310ea006b1c7e2a9c4c5608b85b8f0ef7a14305593a05880e6d11adcb372

Tx prefix hash: a9a945c4086f3631652d36fd7506e4d57049bfe9b83c60ea8d235eeec3392608
Tx public key: f5f49d41d5619a89bae0b516de88c77897ed74a9de43106a0c2b1702c1a63f36
Timestamp: 1672711472 Timestamp [UCT]: 2023-01-03 02:04:32 Age [y:d:h:m:s]: 02:056:21:25:54
Block: 666377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562310 RingCT/type: yes/0
Extra: 01f5f49d41d5619a89bae0b516de88c77897ed74a9de43106a0c2b1702c1a63f3602110000000852542ceb000000000000000000

1 output(s) for total of 3.802036968000 dcy

stealth address amount amount idx
00: f6ec4a3fd798e4e418534555b15a2f274a669e8d27b12c90d0fbee38f1b6ea49 3.802036968000 1107484 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": 666387, "vin": [ { "gen": { "height": 666377 } } ], "vout": [ { "amount": 3802036968, "target": { "key": "f6ec4a3fd798e4e418534555b15a2f274a669e8d27b12c90d0fbee38f1b6ea49" } } ], "extra": [ 1, 245, 244, 157, 65, 213, 97, 154, 137, 186, 224, 181, 22, 222, 136, 199, 120, 151, 237, 116, 169, 222, 67, 16, 106, 12, 43, 23, 2, 193, 166, 63, 54, 2, 17, 0, 0, 0, 8, 82, 84, 44, 235, 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