Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ea7afdf77143cd63be3ba152f653ec8746cd49a05275e4c4aed1973b7418953

Tx prefix hash: 1877906772898f290e99e91d04b24be0c494ceacce7e4a37ad7ee0d46dc57d8e
Tx public key: fafd1f0c10f410114f0f72a15d513c7337923a96178cd06cdd9aa72343f97433
Timestamp: 1751784122 Timestamp [UTC]: 2025-07-06 06:42:02 Age [y:d:h:m:s]: 00:314:07:40:35
Block: 1319769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215382 RingCT/type: yes/0
Extra: 01fafd1f0c10f410114f0f72a15d513c7337923a96178cd06cdd9aa72343f97433021100000002d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4e43260e6351363a218eb93c171794e0f7c534aa6e452f147f9bc889847b7546 0.000600000000 1807462 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": 1319779, "vin": [ { "gen": { "height": 1319769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e43260e6351363a218eb93c171794e0f7c534aa6e452f147f9bc889847b7546" } } ], "extra": [ 1, 250, 253, 31, 12, 16, 244, 16, 17, 79, 15, 114, 161, 93, 81, 60, 115, 55, 146, 58, 150, 23, 140, 208, 108, 221, 154, 167, 35, 67, 249, 116, 51, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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: