Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ae88dcd8aad97b2f3e53e3ddd5dc62f16e2f7e9cf1816d316e5bda29d70404

Tx prefix hash: 0f3135724933c5f16a2bfa9c4550ee86b24b5d90329725760fb64f1e218a8807
Tx public key: 355a0aaf3b7e0882834ffa43de00f2bc4dddc1091eefe6f5d3f2fd4898e70a6e
Timestamp: 1758419875 Timestamp [UTC]: 2025-09-21 01:57:55 Age [y:d:h:m:s]: 01:059:01:20:27
Block: 1372962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308639 RingCT/type: yes/0
Extra: 01355a0aaf3b7e0882834ffa43de00f2bc4dddc1091eefe6f5d3f2fd4898e70a6e021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7fbd2941f8143d1be2cb61dd5721502fca993ed5927867b99e8c4509c7221909 0.000600000000 1861047 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": 1372972, "vin": [ { "gen": { "height": 1372962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fbd2941f8143d1be2cb61dd5721502fca993ed5927867b99e8c4509c7221909" } } ], "extra": [ 1, 53, 90, 10, 175, 59, 126, 8, 130, 131, 79, 250, 67, 222, 0, 242, 188, 77, 221, 193, 9, 30, 239, 230, 245, 211, 242, 253, 72, 152, 231, 10, 110, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: