Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50ce856f7c2037e4e9cec1b54bc1f46742f445f000898b0022eda5e7720b821e

Tx prefix hash: 590156e09e56f83efc2c6d1b038e9a65dbfa9bc355d747ef1f2757a9b687dd13
Tx public key: 6dca07970b298ff38209d44954bc30081619aa6f28869caacd2c87d82a5f26f2
Timestamp: 1720349297 Timestamp [UCT]: 2024-07-07 10:48:17 Age [y:d:h:m:s]: 00:275:18:58:50
Block: 1060448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197046 RingCT/type: yes/0
Extra: 016dca07970b298ff38209d44954bc30081619aa6f28869caacd2c87d82a5f26f2021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45b04f842a2fb07c613f50b978b0189cc730a58e3f3c4dc10905c83d8bf35bfb 0.600000000000 1530931 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": 1060458, "vin": [ { "gen": { "height": 1060448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45b04f842a2fb07c613f50b978b0189cc730a58e3f3c4dc10905c83d8bf35bfb" } } ], "extra": [ 1, 109, 202, 7, 151, 11, 41, 143, 243, 130, 9, 212, 73, 84, 188, 48, 8, 22, 25, 170, 111, 40, 134, 156, 170, 205, 44, 135, 216, 42, 95, 38, 242, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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