Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75309c094f3890996c755cd445eec79ab1df2cb5a464b460a21cb9135f36de0b

Tx prefix hash: a74d6e3a4ea79b7c6aa86b7ada49bcb89fb67442403e9ed62131abd60a2682ed
Tx public key: 150b1820442e760b0e2cc61c9a3083d73f331ca8240a041c4c757831035ea19e
Timestamp: 1741769308 Timestamp [UTC]: 2025-03-12 08:48:28 Age [y:d:h:m:s]: 01:001:07:44:54
Block: 1237579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259482 RingCT/type: yes/0
Extra: 01150b1820442e760b0e2cc61c9a3083d73f331ca8240a041c4c757831035ea19e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cfded6de46ce637d0ed6f6dea0b5db3e508ca6e2d73345ba3be7e0861c306feb 0.000600000000 1724534 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": 1237589, "vin": [ { "gen": { "height": 1237579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cfded6de46ce637d0ed6f6dea0b5db3e508ca6e2d73345ba3be7e0861c306feb" } } ], "extra": [ 1, 21, 11, 24, 32, 68, 46, 118, 11, 14, 44, 198, 28, 154, 48, 131, 215, 63, 51, 28, 168, 36, 10, 4, 28, 76, 117, 120, 49, 3, 94, 161, 158, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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) | dinastycoin version: tesla-369