Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51fc1ae4c350cd6463a351d7eb776cfc3ec88892882f303f04ef77b4c8cfeb68

Tx prefix hash: 3e49cfb3e7a60392738c87fe9804080f80a46027ea0b0c767bc015cb5aca427e
Tx public key: c7e1df8cc368c943d053e8ad1703b48d7f224f7985a69d5eb82eb7b34b687040
Timestamp: 1715392949 Timestamp [UCT]: 2024-05-11 02:02:29 Age [y:d:h:m:s]: 01:042:16:22:37
Block: 1019379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291233 RingCT/type: yes/0
Extra: 01c7e1df8cc368c943d053e8ad1703b48d7f224f7985a69d5eb82eb7b34b68704002110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a0de23c8436253b992301d80b7c46127cfccf0c83096479059d55161e001fbc 0.600000000000 1483332 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": 1019389, "vin": [ { "gen": { "height": 1019379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a0de23c8436253b992301d80b7c46127cfccf0c83096479059d55161e001fbc" } } ], "extra": [ 1, 199, 225, 223, 140, 195, 104, 201, 67, 208, 83, 232, 173, 23, 3, 180, 141, 127, 34, 79, 121, 133, 166, 157, 94, 184, 46, 183, 179, 75, 104, 112, 64, 2, 17, 0, 0, 0, 7, 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