Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66e391a677e7e3a0a68f04bdcf04de5904f8164582115fa5e7b0d783abdde491

Tx prefix hash: 4ef13b4faeac42dc3c5a1ebb84f84862c972b5075472ca00a58275c1ec3b75e2
Tx public key: 1c70fd09dc2ee17eeb5bdcf6e3aee07035a7232dbecf7fca6543bf1d92e2f5cc
Timestamp: 1740482040 Timestamp [UCT]: 2025-02-25 11:14:00 Age [y:d:h:m:s]: 00:269:05:43:41
Block: 1226898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190181 RingCT/type: yes/0
Extra: 011c70fd09dc2ee17eeb5bdcf6e3aee07035a7232dbecf7fca6543bf1d92e2f5cc021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64791617cda4bdfc1e73603dd3366167c1fda52f7e692ad56785f947b389c2c6 0.600000000000 1713771 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": 1226908, "vin": [ { "gen": { "height": 1226898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64791617cda4bdfc1e73603dd3366167c1fda52f7e692ad56785f947b389c2c6" } } ], "extra": [ 1, 28, 112, 253, 9, 220, 46, 225, 126, 235, 91, 220, 246, 227, 174, 224, 112, 53, 167, 35, 45, 190, 207, 127, 202, 101, 67, 191, 29, 146, 226, 245, 204, 2, 17, 0, 0, 0, 7, 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