Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338f2d3dbcba5ae3788fabac8e8c7ed45de5c398d7f5ec0f4408607e2331f82d

Tx prefix hash: e7c7b7d6b92060baff188751c645b47febaa9ef174a9aba2f9e7e09f17d15319
Tx public key: 9d30c7c539b6138c84d03e602ba8cf49faca78283c8e88802edf5bd3a2522fe9
Timestamp: 1729337319 Timestamp [UCT]: 2024-10-19 11:28:39 Age [y:d:h:m:s]: 00:019:17:12:33
Block: 1134962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14045 RingCT/type: yes/0
Extra: 019d30c7c539b6138c84d03e602ba8cf49faca78283c8e88802edf5bd3a2522fe902110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dca814d2e8f0a04817821a0bece95a7d8f86c39ae45fd4f67f0f0c9a35c11f3c 0.600000000000 1618289 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": 1134972, "vin": [ { "gen": { "height": 1134962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dca814d2e8f0a04817821a0bece95a7d8f86c39ae45fd4f67f0f0c9a35c11f3c" } } ], "extra": [ 1, 157, 48, 199, 197, 57, 182, 19, 140, 132, 208, 62, 96, 43, 168, 207, 73, 250, 202, 120, 40, 60, 142, 136, 128, 46, 223, 91, 211, 162, 82, 47, 233, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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