Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa2261dca109e1015caa51cb71e23b90e913e70e7c365667a57bfe585c7ab77b

Tx prefix hash: 9b1c8d6c25367f12dc074a9edd9bc29cf078db64b12b725736bb539165ae5359
Tx public key: 12f80bf458b3ab52f5b61e94f11cff4476a706c4bcda7fd0c4d1a6763d5af8e9
Timestamp: 1785408720 Timestamp [UTC]: 2026-07-30 10:52:00 Age [y:d:h:m:s]: 00:115:06:55:54
Block: 1601703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 81791 RingCT/type: yes/0
Extra: 0112f80bf458b3ab52f5b61e94f11cff4476a706c4bcda7fd0c4d1a6763d5af8e90208f282ef92d9a46071

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3ae3afefb03f4849473bee089153f7093209c70613fccf4c143778d6c5638a1d 0.000600000000 2091721 of 15 <ab>

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": 1601713, "vin": [ { "gen": { "height": 1601703 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "3ae3afefb03f4849473bee089153f7093209c70613fccf4c143778d6c5638a1d", "view_tag": "ab" } } } ], "extra": [ 1, 18, 248, 11, 244, 88, 179, 171, 82, 245, 182, 30, 148, 241, 28, 255, 68, 118, 167, 6, 196, 188, 218, 127, 208, 196, 209, 166, 118, 61, 90, 248, 233, 2, 8, 242, 130, 239, 146, 217, 164, 96, 113 ], "rct_signatures": { "type": 0 } }


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