Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ee689978f957d6f7807d3c9786e1cb9338e9b1d08db77cd5cd407bcc509d6fc

Tx prefix hash: d5563202cf8c1c047500e8254a1c44959cf58075e845272aa8e3ecfd87d6b693
Tx public key: db7db6038b5eea9cbda7f794ad375de732a1a982dc2f56ea6b3b201e704c1acc
Timestamp: 1708998474 Timestamp [UCT]: 2024-02-27 01:47:54 Age [y:d:h:m:s]: 01:021:09:49:37
Block: 966356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276318 RingCT/type: yes/0
Extra: 01db7db6038b5eea9cbda7f794ad375de732a1a982dc2f56ea6b3b201e704c1acc02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcf54565914a92a6992815b688e89d52ff986c7e13b1e26b2325d61ee9a7d223 0.600000000000 1426113 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": 966366, "vin": [ { "gen": { "height": 966356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcf54565914a92a6992815b688e89d52ff986c7e13b1e26b2325d61ee9a7d223" } } ], "extra": [ 1, 219, 125, 182, 3, 139, 94, 234, 156, 189, 167, 247, 148, 173, 55, 93, 231, 50, 161, 169, 130, 220, 47, 86, 234, 107, 59, 32, 30, 112, 76, 26, 204, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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