Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6799c68151c34d339e0c706b471aa99ab4bb9fc66d17e89d6c282b62400b562

Tx prefix hash: 2e4a47d9ce869ae8ee4189b110c09ee09acf9bac3f631bba6a24b54834dc0bd9
Tx public key: 0f43075450c672c835417a648c8b47dfdc4a0ac19016002251087cf4c876d141
Timestamp: 1658162819 Timestamp [UCT]: 2022-07-18 16:46:59 Age [y:d:h:m:s]: 02:245:05:32:10
Block: 546536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 696462 RingCT/type: yes/0
Extra: 010f43075450c672c835417a648c8b47dfdc4a0ac19016002251087cf4c876d141021100000002d3fcec30000000000000000000

1 output(s) for total of 9.486357591000 dcy

stealth address amount amount idx
00: 6699a6ddea4caf9257d3b4924a95485c7a50ccb5e0da58b0f4c0d8e25054029e 9.486357591000 977565 of 0

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": 546546, "vin": [ { "gen": { "height": 546536 } } ], "vout": [ { "amount": 9486357591, "target": { "key": "6699a6ddea4caf9257d3b4924a95485c7a50ccb5e0da58b0f4c0d8e25054029e" } } ], "extra": [ 1, 15, 67, 7, 84, 80, 198, 114, 200, 53, 65, 122, 100, 140, 139, 71, 223, 220, 74, 10, 193, 144, 22, 0, 34, 81, 8, 124, 244, 200, 118, 209, 65, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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