Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52a3acd12fb0c7b25b11fc2e9ee88b8c522de290dea1096f0e81ef8b7e998a4c

Tx prefix hash: 9f2edd557dc32e1b805943edd38a23c7ca2cb4d9ae015a65f3cb98254a8bd1ef
Tx public key: e695bc69b89faddad340e57d749ba6486dc84aa7a5d0d4059fc82b0fc7886f88
Timestamp: 1712603832 Timestamp [UCT]: 2024-04-08 19:17:12 Age [y:d:h:m:s]: 00:322:17:00:45
Block: 996206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230717 RingCT/type: yes/0
Extra: 01e695bc69b89faddad340e57d749ba6486dc84aa7a5d0d4059fc82b0fc7886f8802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c1b40d7b0d1ea007943fd94c2c3e8210534e01c1a897b2ebf20d20ad0552fb 0.600000000000 1456622 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": 996216, "vin": [ { "gen": { "height": 996206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c1b40d7b0d1ea007943fd94c2c3e8210534e01c1a897b2ebf20d20ad0552fb" } } ], "extra": [ 1, 230, 149, 188, 105, 184, 159, 173, 218, 211, 64, 229, 125, 116, 155, 166, 72, 109, 200, 74, 167, 165, 208, 212, 5, 159, 200, 43, 15, 199, 136, 111, 136, 2, 17, 0, 0, 0, 3, 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