Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac43e60b447fcada000886a4b6250e642f4e3c200e3b89d04ce0d60c90777e7

Tx prefix hash: bd169da26c555ebc970b9e664f693ef8e7321fbbf3832a728bea76b305e59e8a
Tx public key: 46a19f30047b8cbf4015d792c8cc1dffc19dd8ad879a963fda18e1f3d0a70668
Timestamp: 1709909616 Timestamp [UTC]: 2024-03-08 14:53:36 Age [y:d:h:m:s]: 02:257:20:58:52
Block: 973906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709483 RingCT/type: yes/0
Extra: 0146a19f30047b8cbf4015d792c8cc1dffc19dd8ad879a963fda18e1f3d0a706680211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 752a10131012f6b1399163033cd8965f577fa68905cc7171256a8074c3241a20 0.000600000000 1433849 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": 973916, "vin": [ { "gen": { "height": 973906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "752a10131012f6b1399163033cd8965f577fa68905cc7171256a8074c3241a20" } } ], "extra": [ 1, 70, 161, 159, 48, 4, 123, 140, 191, 64, 21, 215, 146, 200, 204, 29, 255, 193, 157, 216, 173, 135, 154, 150, 63, 218, 24, 225, 243, 208, 167, 6, 104, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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: