Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 262e49558e102457eaee9f708b6f6e47185a7d736cce159be4c0289d095b7035

Tx prefix hash: 46876d3fc0566b6b1d50cc3cb70d91205e697fc1296f6ac9cb85ed936b38d684
Tx public key: 81ecad54e91130ed4ce052d14984c312adcc0edd64198e818d5928d9e8dc49e2
Timestamp: 1771458698 Timestamp [UTC]: 2026-02-18 23:51:38 Age [y:d:h:m:s]: 00:276:19:17:05
Block: 1480824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202670 RingCT/type: yes/0
Extra: 0181ecad54e91130ed4ce052d14984c312adcc0edd64198e818d5928d9e8dc49e2021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3604cff8a91e022ed7338de92f3b3c33e6679f41ddcec88b6a2911f1bb937924 0.000600000000 1970196 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": 1480834, "vin": [ { "gen": { "height": 1480824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3604cff8a91e022ed7338de92f3b3c33e6679f41ddcec88b6a2911f1bb937924" } } ], "extra": [ 1, 129, 236, 173, 84, 233, 17, 48, 237, 76, 224, 82, 209, 73, 132, 195, 18, 173, 204, 14, 221, 100, 25, 142, 129, 141, 89, 40, 217, 232, 220, 73, 226, 2, 17, 0, 0, 0, 9, 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: