Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d4727148e20e33ec3278ccfe3daceb6d4d1969b67bf77cc83fce6c8f9653df

Tx prefix hash: 64f1fc53ce4e28dfd129f879d52f9e2221b483e10e75748a73b3048ddd242584
Tx public key: 06b7d5e8cc8ee27de7e80e81889a86dd7fb65b5a86f2abf32a57e70e53b0c202
Timestamp: 1708599062 Timestamp [UCT]: 2024-02-22 10:51:02 Age [y:d:h:m:s]: 01:040:06:26:11
Block: 963039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289794 RingCT/type: yes/0
Extra: 0106b7d5e8cc8ee27de7e80e81889a86dd7fb65b5a86f2abf32a57e70e53b0c2020211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23141ab1d6ccd9e63918a23239ce82568c82312aa63a05bb9a250ec01e8d170c 0.600000000000 1422736 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": 963049, "vin": [ { "gen": { "height": 963039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23141ab1d6ccd9e63918a23239ce82568c82312aa63a05bb9a250ec01e8d170c" } } ], "extra": [ 1, 6, 183, 213, 232, 204, 142, 226, 125, 231, 232, 14, 129, 136, 154, 134, 221, 127, 182, 91, 90, 134, 242, 171, 243, 42, 87, 231, 14, 83, 176, 194, 2, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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