Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fcf5fd09e1cc78e43383b8f35498f98d9aed4fa5b1ec648bcd1b0e9b2cde071

Tx prefix hash: a61f367496eed88172797b240291ab91459b6e1466322abbe9a149b1b95ec5ea
Tx public key: 73b26f0a08f461ecb0035819be3d56b59d0827e6367ed04188ad6e063d20b6cf
Timestamp: 1764399609 Timestamp [UTC]: 2025-11-29 07:00:09 Age [y:d:h:m:s]: 00:350:16:18:17
Block: 1422525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255947 RingCT/type: yes/0
Extra: 0173b26f0a08f461ecb0035819be3d56b59d0827e6367ed04188ad6e063d20b6cf02110000000134af31cc000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c4f8250c4f0f35748e44f4adf010d4ccc55a3124b1e9e67ace98c4359d78ed31 0.000600000000 1911092 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": 1422535, "vin": [ { "gen": { "height": 1422525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4f8250c4f0f35748e44f4adf010d4ccc55a3124b1e9e67ace98c4359d78ed31" } } ], "extra": [ 1, 115, 178, 111, 10, 8, 244, 97, 236, 176, 3, 88, 25, 190, 61, 86, 181, 157, 8, 39, 230, 54, 126, 208, 65, 136, 173, 110, 6, 61, 32, 182, 207, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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: