Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 432e7d33404516d39723aa83d1c3aad0ad6e3b9ae0ab4b2a22d5d6f926adf5c8

Tx prefix hash: 5c6a8ad0ea6a9c887133c7229d81994bcb36b163be5f4f3fbb7b8dc2bcb7c7a7
Tx public key: defe7884c5138e29429b32044d24812396202cb4bcaca72b39517600297163be
Timestamp: 1722680794 Timestamp [UCT]: 2024-08-03 10:26:34 Age [y:d:h:m:s]: 00:270:16:22:45
Block: 1079778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193357 RingCT/type: yes/0
Extra: 01defe7884c5138e29429b32044d24812396202cb4bcaca72b39517600297163be021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd4b3d3b6200ebc9b4c90f8f710eb01dddc5ff1eb7c0aed3bc7e0ffbff6e652b 0.600000000000 1552883 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": 1079788, "vin": [ { "gen": { "height": 1079778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd4b3d3b6200ebc9b4c90f8f710eb01dddc5ff1eb7c0aed3bc7e0ffbff6e652b" } } ], "extra": [ 1, 222, 254, 120, 132, 197, 19, 142, 41, 66, 155, 50, 4, 77, 36, 129, 35, 150, 32, 44, 180, 188, 172, 167, 43, 57, 81, 118, 0, 41, 113, 99, 190, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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