Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3443587366b6c3e92488f0f3f65d8d1794d28b55d2fb606169be7aa5b923213

Tx prefix hash: 7cd3ce37525ddde276e3673d8d57ad165881b5e07728cd39f74df379129b84cd
Tx public key: fcefde0a110a14b2c9948d546b5e16d9e591112acdbe9be873c7665b4bace2f7
Timestamp: 1706242503 Timestamp [UCT]: 2024-01-26 04:15:03 Age [y:d:h:m:s]: 00:293:17:51:59
Block: 943469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210353 RingCT/type: yes/0
Extra: 01fcefde0a110a14b2c9948d546b5e16d9e591112acdbe9be873c7665b4bace2f70211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33fe87a0c18a1196e6519b03fe01b39bb419b3cbfc5bed3e1551036ef1ab9d9f 0.600000000000 1401675 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": 943479, "vin": [ { "gen": { "height": 943469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33fe87a0c18a1196e6519b03fe01b39bb419b3cbfc5bed3e1551036ef1ab9d9f" } } ], "extra": [ 1, 252, 239, 222, 10, 17, 10, 20, 178, 201, 148, 141, 84, 107, 94, 22, 217, 229, 145, 17, 42, 205, 190, 155, 232, 115, 199, 102, 91, 75, 172, 226, 247, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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