Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecfc0be0ecae786085aa2d60c6ee224572d2d1e1fd9ed12b181cf606f5f4895

Tx prefix hash: abcaa43469febd4d2b4d6f9fa7554655bb66b16b6f68ccef7a7854e68e2bedb2
Tx public key: 953420f06366a96b024760d3ef882d7f3221698ce5173d122b16f23c5d091712
Timestamp: 1635641673 Timestamp [UCT]: 2021-10-31 00:54:33 Age [y:d:h:m:s]: 04:053:10:01:55
Block: 363988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075112 RingCT/type: yes/0
Extra: 01953420f06366a96b024760d3ef882d7f3221698ce5173d122b16f23c5d0917120211000000194f792ffd000000000000000000

1 output(s) for total of 38.190650916000 dcy

stealth address amount amount idx
00: 30948bb372b430839615ce6f6c4fd953b1762ea583a8ff261c20d08e0f80fe1f 38.190650916000 739592 of 0

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": 363998, "vin": [ { "gen": { "height": 363988 } } ], "vout": [ { "amount": 38190650916, "target": { "key": "30948bb372b430839615ce6f6c4fd953b1762ea583a8ff261c20d08e0f80fe1f" } } ], "extra": [ 1, 149, 52, 32, 240, 99, 102, 169, 107, 2, 71, 96, 211, 239, 136, 45, 127, 50, 33, 105, 140, 229, 23, 61, 18, 43, 22, 242, 60, 93, 9, 23, 18, 2, 17, 0, 0, 0, 25, 79, 121, 47, 253, 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