Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d57da804b34015671965efdc4ba4e45db51034201aeba9de38c164342e3308

Tx prefix hash: 8490f12d0af2732ddddfdb856a28a330dcae306886e4626f0d2d70ee1c5c8cec
Tx public key: 10fc91190deb620da2510e8c9cf88e9c5dfa07b97d2d525a8150da54150ab9e0
Timestamp: 1772417451 Timestamp [UTC]: 2026-03-02 02:10:51 Age [y:d:h:m:s]: 00:264:13:10:58
Block: 1488757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194735 RingCT/type: yes/0
Extra: 0110fc91190deb620da2510e8c9cf88e9c5dfa07b97d2d525a8150da54150ab9e0021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf602055ed98e53204f8be40b84b2ab68a24bdcf4edf066ce2b9e181873af892 0.000600000000 1978237 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": 1488767, "vin": [ { "gen": { "height": 1488757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf602055ed98e53204f8be40b84b2ab68a24bdcf4edf066ce2b9e181873af892" } } ], "extra": [ 1, 16, 252, 145, 25, 13, 235, 98, 13, 162, 81, 14, 140, 156, 248, 142, 156, 93, 250, 7, 185, 125, 45, 82, 90, 129, 80, 218, 84, 21, 10, 185, 224, 2, 17, 0, 0, 0, 6, 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: