Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe796b50b606dbdb8e5e3b91e926e2372e246c7f58f84e5c01efb60fc193e994

Tx prefix hash: 430c91497cd56a631e8c3c933d9013f9300dd4eba1806716547d46d8b56bcdd7
Tx public key: d1709c0338245a4db8cde6374753f061d6a7531e6b5e7f506a006cef1aae4fd9
Timestamp: 1760388019 Timestamp [UTC]: 2025-10-13 20:40:19 Age [y:d:h:m:s]: 01:032:21:21:27
Block: 1389290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289775 RingCT/type: yes/0
Extra: 01d1709c0338245a4db8cde6374753f061d6a7531e6b5e7f506a006cef1aae4fd90211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a677c0cdab107d062b174c0a79ac6c7fbd732fe8f5044ba367d20940165476e4 0.000600000000 1877519 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": 1389300, "vin": [ { "gen": { "height": 1389290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a677c0cdab107d062b174c0a79ac6c7fbd732fe8f5044ba367d20940165476e4" } } ], "extra": [ 1, 209, 112, 156, 3, 56, 36, 90, 77, 184, 205, 230, 55, 71, 83, 240, 97, 214, 167, 83, 30, 107, 94, 127, 80, 106, 0, 108, 239, 26, 174, 79, 217, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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: