Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b4ff1a773bb16db1ca66f3420a54641738bc97579330a2bae1a2e21053ed62

Tx prefix hash: 4ca75b0fa12e9d16cde691610c6d5fed11db595f1d005b5af2e83c29fee1b6bb
Tx public key: e70d96d4e692019e631055a27ca403a2c63c727d41e883d6162d6238cc2d01f9
Timestamp: 1685345125 Timestamp [UTC]: 2023-05-29 07:25:25 Age [y:d:h:m:s]: 02:350:00:15:43
Block: 770504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762193 RingCT/type: yes/0
Extra: 01e70d96d4e692019e631055a27ca403a2c63c727d41e883d6162d6238cc2d01f9021100000002faf35c9c000000000000000000

1 output(s) for total of 0.001717910641 xmr

stealth address amount amount idx tag
00: 467cf86a78e6e971f56b25c3532046f4f7a9276c19bc7264304775b029667515 0.001717910641 1219811 of 0 -

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": 770514, "vin": [ { "gen": { "height": 770504 } } ], "vout": [ { "amount": 1717910641, "target": { "key": "467cf86a78e6e971f56b25c3532046f4f7a9276c19bc7264304775b029667515" } } ], "extra": [ 1, 231, 13, 150, 212, 230, 146, 1, 158, 99, 16, 85, 162, 124, 164, 3, 162, 198, 60, 114, 125, 65, 232, 131, 214, 22, 45, 98, 56, 204, 45, 1, 249, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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: