Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05c1254f6c977b29b5e691d5aec0d93dfeade702c66d78ca5a699dde618508b2

Tx prefix hash: 6954938e80b46287134d2179fb6834fd4ccc6cee0415b315f1c4f65ba717d88e
Tx public key: 7ba773397307c14217ddf8d11735bf61c56f8cff90961c00b112ece64b6d5ea9
Timestamp: 1771454611 Timestamp [UTC]: 2026-02-18 22:43:31 Age [y:d:h:m:s]: 00:272:03:39:51
Block: 1480790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200021 RingCT/type: yes/0
Extra: 017ba773397307c14217ddf8d11735bf61c56f8cff90961c00b112ece64b6d5ea902110000000ae4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c693651b6a72ee82baf688b644e11fa57d8b913766ae7a28f25029363db1100f 0.000600000000 1970162 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": 1480800, "vin": [ { "gen": { "height": 1480790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c693651b6a72ee82baf688b644e11fa57d8b913766ae7a28f25029363db1100f" } } ], "extra": [ 1, 123, 167, 115, 57, 115, 7, 193, 66, 23, 221, 248, 209, 23, 53, 191, 97, 197, 111, 140, 255, 144, 150, 28, 0, 177, 18, 236, 230, 75, 109, 94, 169, 2, 17, 0, 0, 0, 10, 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: