Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf63c34e759021f0d4abae8a7caf10b293eba49ded4caf6a2d08ae54d9f61bc

Tx prefix hash: b490c0d2af125f564d27ebe23da7f7c5a7763b6782e87a1f31d9edad83a4c9fd
Tx public key: f8630023a442be6d0663bd0b721a86fb62c20b62b72fda4c355badc176f04d78
Timestamp: 1772495654 Timestamp [UTC]: 2026-03-02 23:54:14 Age [y:d:h:m:s]: 00:263:06:51:13
Block: 1489398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193836 RingCT/type: yes/0
Extra: 01f8630023a442be6d0663bd0b721a86fb62c20b62b72fda4c355badc176f04d78021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fcb1b3c0925c7d9089777066071cf1a8b831c51ae6c1c127289df6906193e07e 0.000600000000 1978888 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": 1489408, "vin": [ { "gen": { "height": 1489398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcb1b3c0925c7d9089777066071cf1a8b831c51ae6c1c127289df6906193e07e" } } ], "extra": [ 1, 248, 99, 0, 35, 164, 66, 190, 109, 6, 99, 189, 11, 114, 26, 134, 251, 98, 194, 11, 98, 183, 47, 218, 76, 53, 91, 173, 193, 118, 240, 77, 120, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: