Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b16650b4042711a6e45d981a3bee74c56d1ff7573cd2b8e0ff464e7507e2c1f8

Tx prefix hash: 652aa22c11f0a2394a9138f6204121c687b9b917e0c7142901b0f88fd6c3a54a
Tx public key: 14a62635df7a1770bb9d70b2aa4f5726e7071b830eefff44d7b7e6e58afa5faf
Timestamp: 1770050101 Timestamp [UTC]: 2026-02-02 16:35:01 Age [y:d:h:m:s]: 00:290:06:13:38
Block: 1469170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213051 RingCT/type: yes/0
Extra: 0114a62635df7a1770bb9d70b2aa4f5726e7071b830eefff44d7b7e6e58afa5faf021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c401c046284a42be712b3d9690fd9eb2f132647093ca79db13347152c45057f7 0.000600000000 1958424 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": 1469180, "vin": [ { "gen": { "height": 1469170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c401c046284a42be712b3d9690fd9eb2f132647093ca79db13347152c45057f7" } } ], "extra": [ 1, 20, 166, 38, 53, 223, 122, 23, 112, 187, 157, 112, 178, 170, 79, 87, 38, 231, 7, 27, 131, 14, 239, 255, 68, 215, 183, 230, 229, 138, 250, 95, 175, 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: