Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caaed04ad3ba79e829f45b2b561233eb38482fc0882ab112689c1c6d919e91e5

Tx prefix hash: e6cbd182ea4bbe26729e70a9543b90487a197bca69dad5b32937e38f645477e7
Tx public key: d3bb549bb1e45eb4d021bdd74a0c0c82fc1d11781ae9a65636c760aea6460110
Timestamp: 1718815506 Timestamp [UCT]: 2024-06-19 16:45:06 Age [y:d:h:m:s]: 00:330:11:36:56
Block: 1047733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236181 RingCT/type: yes/0
Extra: 01d3bb549bb1e45eb4d021bdd74a0c0c82fc1d11781ae9a65636c760aea64601100211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6c5025e7e499829cb82ce4e1e3acf917703cdcd3e7485dd8df7086f246eac4a 0.600000000000 1517632 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": 1047743, "vin": [ { "gen": { "height": 1047733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6c5025e7e499829cb82ce4e1e3acf917703cdcd3e7485dd8df7086f246eac4a" } } ], "extra": [ 1, 211, 187, 84, 155, 177, 228, 94, 180, 208, 33, 189, 215, 74, 12, 12, 130, 252, 29, 17, 120, 26, 233, 166, 86, 54, 199, 96, 174, 166, 70, 1, 16, 2, 17, 0, 0, 0, 1, 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