Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5b4dd1df427a953f010e955b9a0e1dfaeb64fcc33618879f4bb72a377d2c71

Tx prefix hash: d23f64ad441e08af2d50c7ebbbab285379a315532d4e0117d352d2831f4e75f5
Tx public key: 7ec76d694271ee23e5746e5842338d1f3f257a099e2f480afe83f3ca0275ec45
Timestamp: 1785438648 Timestamp [UTC]: 2026-07-30 19:10:48 Age [y:d:h:m:s]: 00:112:18:05:30
Block: 1601950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 80767 RingCT/type: yes/0
Extra: 017ec76d694271ee23e5746e5842338d1f3f257a099e2f480afe83f3ca0275ec4502080fcef62f6c0cf1e9

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ee5f0c0a322d8554a7ccd3734924dfddff135b8c258962f0558a574d4d7916a 0.000600000000 2091968 of 15 <69>

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": 1601960, "vin": [ { "gen": { "height": 1601950 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "5ee5f0c0a322d8554a7ccd3734924dfddff135b8c258962f0558a574d4d7916a", "view_tag": "69" } } } ], "extra": [ 1, 126, 199, 109, 105, 66, 113, 238, 35, 229, 116, 110, 88, 66, 51, 141, 31, 63, 37, 122, 9, 158, 47, 72, 10, 254, 131, 243, 202, 2, 117, 236, 69, 2, 8, 15, 206, 246, 47, 108, 12, 241, 233 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: