Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d65fd604b986409ae33871df048f2768c5ba8a91b2085aefc2448c5a4c75e3df

Tx prefix hash: 9c50304a6005ab570d60a1f0b4d725bf4b9dac2bafaa1f28f640c3923d4e38db
Tx public key: e892b050ae4b58578b9657f04a1a841159536ca8e0da1ea6af4108db4331d660
Timestamp: 1712893025 Timestamp [UCT]: 2024-04-12 03:37:05 Age [y:d:h:m:s]: 00:362:05:54:46
Block: 998611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259000 RingCT/type: yes/0
Extra: 01e892b050ae4b58578b9657f04a1a841159536ca8e0da1ea6af4108db4331d6600211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c738774edbd77cdbe339886839e1da2edcb242246fae4c5c628dd9057b41b49 0.600000000000 1459063 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": 998621, "vin": [ { "gen": { "height": 998611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c738774edbd77cdbe339886839e1da2edcb242246fae4c5c628dd9057b41b49" } } ], "extra": [ 1, 232, 146, 176, 80, 174, 75, 88, 87, 139, 150, 87, 240, 74, 26, 132, 17, 89, 83, 108, 168, 224, 218, 30, 166, 175, 65, 8, 219, 67, 49, 214, 96, 2, 17, 0, 0, 0, 1, 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