Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7edab9fcbeb29ed0d1c59205a4c8e61fac06cc36f87153bc3cb8cf51c791fb

Tx prefix hash: c7bc7c55aa08e9a0dd7f483d39ecce08b35182a653418a303d1d7e7fd03656ed
Tx public key: a2956ead11d7f8a2d5f2efea63009ff0bf94973338009f9218dc96b290847ca1
Timestamp: 1762682779 Timestamp [UTC]: 2025-11-09 10:06:19 Age [y:d:h:m:s]: 01:007:18:31:19
Block: 1408294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271852 RingCT/type: yes/0
Extra: 01a2956ead11d7f8a2d5f2efea63009ff0bf94973338009f9218dc96b290847ca1021100000002df5a247a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 55fe0ab13b0e4b1e5bcbd35330d6f17530cbc0aee7aae1c6be2daffb2384144a 0.000600000000 1896723 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": 1408304, "vin": [ { "gen": { "height": 1408294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55fe0ab13b0e4b1e5bcbd35330d6f17530cbc0aee7aae1c6be2daffb2384144a" } } ], "extra": [ 1, 162, 149, 110, 173, 17, 215, 248, 162, 213, 242, 239, 234, 99, 0, 159, 240, 191, 148, 151, 51, 56, 0, 159, 146, 24, 220, 150, 178, 144, 132, 124, 161, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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: