Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 735d4cbf351afde02291435a4dc819cc09ca0ca04a6e053f349f8caa7ea5a55b

Tx prefix hash: 83446bd0352f9315765688d67133aef432783b307550243b5a0cf1fefaf0717e
Tx public key: fd7b7d35663694829c7b5c67ffb70676bb37b2c3adc72e35111ebcb78c240b97
Timestamp: 1739538399 Timestamp [UTC]: 2025-02-14 13:06:39 Age [y:d:h:m:s]: 01:275:05:17:16
Block: 1219104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460720 RingCT/type: yes/0
Extra: 01fd7b7d35663694829c7b5c67ffb70676bb37b2c3adc72e35111ebcb78c240b97021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 41c7f63458338b9e925cf0d3301b5961e27e10be1867f8ce9ec79b4ae2b2d58c 0.000600000000 1705927 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 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": 1219114, "vin": [ { "gen": { "height": 1219104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41c7f63458338b9e925cf0d3301b5961e27e10be1867f8ce9ec79b4ae2b2d58c" } } ], "extra": [ 1, 253, 123, 125, 53, 102, 54, 148, 130, 156, 123, 92, 103, 255, 183, 6, 118, 187, 55, 178, 195, 173, 199, 46, 53, 17, 30, 188, 183, 140, 36, 11, 151, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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: