Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bafc7776f426a87baf74a95c9a66629c5eecb75e49a95bc4e4a30bce54db13d1

Tx prefix hash: 444c14e116e7859f6ebe749fb440cb995bd5b2db7a72d5cda939988f3c1fb8b7
Tx public key: 7ac21e7ad1501d0cea564b849d54a759a585bf82f756d7d6468c730c6bae3407
Timestamp: 1760254231 Timestamp [UTC]: 2025-10-12 07:30:31 Age [y:d:h:m:s]: 01:032:01:30:33
Block: 1388159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289115 RingCT/type: yes/0
Extra: 017ac21e7ad1501d0cea564b849d54a759a585bf82f756d7d6468c730c6bae3407021100000002163191ee000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a1d95e135d60c2d679faeee80fe00b2712b554a310d9aaddf0e11d746021eea 0.000600000000 1876354 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": 1388169, "vin": [ { "gen": { "height": 1388159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a1d95e135d60c2d679faeee80fe00b2712b554a310d9aaddf0e11d746021eea" } } ], "extra": [ 1, 122, 194, 30, 122, 209, 80, 29, 12, 234, 86, 75, 132, 157, 84, 167, 89, 165, 133, 191, 130, 247, 86, 215, 214, 70, 140, 115, 12, 107, 174, 52, 7, 2, 17, 0, 0, 0, 2, 22, 49, 145, 238, 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: