Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cb54b330f4ec306900525a86d682b226cf2fb58fc402de0249f9dfdc8cd5156

Tx prefix hash: b4cd9ef38e3f60cb371ff292c536d68003516a7f290c8aaef3db8ba9d6f52d4a
Tx public key: 7f6530ae11704dad79a7a4fcd9dc4c591a8f65d024098b84c2e8b3883b624259
Timestamp: 1709102132 Timestamp [UCT]: 2024-02-28 06:35:32 Age [y:d:h:m:s]: 01:042:14:46:11
Block: 967212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291466 RingCT/type: yes/0
Extra: 017f6530ae11704dad79a7a4fcd9dc4c591a8f65d024098b84c2e8b3883b6242590211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 749722b3490959c7494bf8e3dfc8867b8e7b5e44c467a2deeb89002f19e1b387 0.600000000000 1426983 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": 967222, "vin": [ { "gen": { "height": 967212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "749722b3490959c7494bf8e3dfc8867b8e7b5e44c467a2deeb89002f19e1b387" } } ], "extra": [ 1, 127, 101, 48, 174, 17, 112, 77, 173, 121, 167, 164, 252, 217, 220, 76, 89, 26, 143, 101, 208, 36, 9, 139, 132, 194, 232, 179, 136, 59, 98, 66, 89, 2, 17, 0, 0, 0, 5, 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