Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9146fbfb544a5e06879e078ecc3c7024658d8aa1bf0373620fcc1bd023d45ea8

Tx prefix hash: 687e759fbe2fd0f84076726c4fe27e73d9f6c78b8fab1f2bbc5a71c37335e4f4
Tx public key: e515e75974f20f730d88aecd2e9329a07adb13216e68dab0b7e725cc9a2b1fb7
Timestamp: 1720212471 Timestamp [UCT]: 2024-07-05 20:47:51 Age [y:d:h:m:s]: 00:272:05:24:51
Block: 1059313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194495 RingCT/type: yes/0
Extra: 01e515e75974f20f730d88aecd2e9329a07adb13216e68dab0b7e725cc9a2b1fb702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a663142a39ea5ecaec348f4e6560fd6754570663611aa78e1a7b38bd1e4f142c 0.600000000000 1529780 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": 1059323, "vin": [ { "gen": { "height": 1059313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a663142a39ea5ecaec348f4e6560fd6754570663611aa78e1a7b38bd1e4f142c" } } ], "extra": [ 1, 229, 21, 231, 89, 116, 242, 15, 115, 13, 136, 174, 205, 46, 147, 41, 160, 122, 219, 19, 33, 110, 104, 218, 176, 183, 231, 37, 204, 154, 43, 31, 183, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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