Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: feaf99b8763005f45f74ccc5bf83c5cd472050aec88dad55555b8bf31a8e6e80

Tx prefix hash: 35a41bfc6f4ccd3a0c1c5901c5e5ccf3a77c4271493a5dc2f416a0b6fd0fce89
Tx public key: c23cf63bd521a8b5d160cf1b3f55cb57706cc9b8fff1bad443ec30cf78cbed3c
Timestamp: 1635578353 Timestamp [UTC]: 2021-10-30 07:19:13 Age [y:d:h:m:s]: 05:024:08:33:43
Block: 363480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1320014 RingCT/type: yes/0
Extra: 01c23cf63bd521a8b5d160cf1b3f55cb57706cc9b8fff1bad443ec30cf78cbed3c02110000000f6a2c97e6000000000000000000

1 output(s) for total of 0.038338955435 xmr

stealth address amount amount idx tag
00: d4a53be09f2b52543035865b64944cc3ef0b112f3dd42e1b7909c71e156e574e 0.038338955435 738734 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 dinastycoin-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": 363490, "vin": [ { "gen": { "height": 363480 } } ], "vout": [ { "amount": 38338955435, "target": { "key": "d4a53be09f2b52543035865b64944cc3ef0b112f3dd42e1b7909c71e156e574e" } } ], "extra": [ 1, 194, 60, 246, 59, 213, 33, 168, 181, 209, 96, 207, 27, 63, 85, 203, 87, 112, 108, 201, 184, 255, 241, 186, 212, 67, 236, 48, 207, 120, 203, 237, 60, 2, 17, 0, 0, 0, 15, 106, 44, 151, 230, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: