Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa9f44f77b32d593d274d162f143f400826b3cb2253b0d60eeb9692e0fc217f0

Tx prefix hash: fa7ec38413c69c8a114c80a28a956e30c5ff82c2e9d45d52e2c7cece806eeb0a
Tx public key: b50c5bea9d05af1e0100f17985241da950a93dde65e070f8ae1e7deb9cd26b2b
Timestamp: 1754982812 Timestamp [UTC]: 2025-08-12 07:13:32 Age [y:d:h:m:s]: 01:099:16:25:44
Block: 1345300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336940 RingCT/type: yes/0
Extra: 01b50c5bea9d05af1e0100f17985241da950a93dde65e070f8ae1e7deb9cd26b2b021100000003e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c77cd0f9cef601fb5841d3273fc0c67c5e485860474d12f4be5f8cb44b6ca43e 0.000600000000 1833193 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": 1345310, "vin": [ { "gen": { "height": 1345300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c77cd0f9cef601fb5841d3273fc0c67c5e485860474d12f4be5f8cb44b6ca43e" } } ], "extra": [ 1, 181, 12, 91, 234, 157, 5, 175, 30, 1, 0, 241, 121, 133, 36, 29, 169, 80, 169, 61, 222, 101, 224, 112, 248, 174, 30, 125, 235, 156, 210, 107, 43, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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: