Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0eb3a4a97ca21f5bfc505dd87b4a13c74b77ccd4d5a1fd8163d010a7348a20

Tx prefix hash: 17d77d830fd5e3bcd2b3736bef0853e8059a8b59adf16f4b4afc8e684a8eac68
Tx public key: a4fc7aa3c5a70dcc0a79ff9517d2060907e3d70900c3375a9957f04a1945a0d4
Timestamp: 1771593875 Timestamp [UTC]: 2026-02-20 13:24:35 Age [y:d:h:m:s]: 00:271:02:33:49
Block: 1481944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199282 RingCT/type: yes/0
Extra: 01a4fc7aa3c5a70dcc0a79ff9517d2060907e3d70900c3375a9957f04a1945a0d4021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 466b5b4b90e6b5548709361170f3984a971fa0bab1dd43b728ea1e40a542fabb 0.000600000000 1971330 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": 1481954, "vin": [ { "gen": { "height": 1481944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "466b5b4b90e6b5548709361170f3984a971fa0bab1dd43b728ea1e40a542fabb" } } ], "extra": [ 1, 164, 252, 122, 163, 197, 167, 13, 204, 10, 121, 255, 149, 23, 210, 6, 9, 7, 227, 215, 9, 0, 195, 55, 90, 153, 87, 240, 74, 25, 69, 160, 212, 2, 17, 0, 0, 0, 4, 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: