Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0393fb87e9f706ad4a6eeec4891c859d4f5b5f884a7f4de9e94fdc37ca144699

Tx prefix hash: e4290e148936bcc2c8f492c08212d80e8a278bc7b82401c003cdf2299288b294
Tx public key: 0f0efa42ecd489f198ee342af5c93685d4ec2c576200942550ccd8ef84f0ab5b
Timestamp: 1718446235 Timestamp [UCT]: 2024-06-15 10:10:35 Age [y:d:h:m:s]: 00:255:13:48:10
Block: 1044686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182586 RingCT/type: yes/0
Extra: 010f0efa42ecd489f198ee342af5c93685d4ec2c576200942550ccd8ef84f0ab5b0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a234e5308b0f3ea81c1abbca546778bd0167c56ace6773e4c2dbd5c8a77c904 0.600000000000 1514061 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": 1044696, "vin": [ { "gen": { "height": 1044686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a234e5308b0f3ea81c1abbca546778bd0167c56ace6773e4c2dbd5c8a77c904" } } ], "extra": [ 1, 15, 14, 250, 66, 236, 212, 137, 241, 152, 238, 52, 42, 245, 201, 54, 133, 212, 236, 44, 87, 98, 0, 148, 37, 80, 204, 216, 239, 132, 240, 171, 91, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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