Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768cf175d23e58f4f6f6aa3d60fe82cf18c6a52e99ca361361ed871a4dd34c95

Tx prefix hash: c2f669771ce92c7fb5b02157604a4b0d794bf6de3c9642e1f004d6fdc4e5a4c6
Tx public key: 7a4ad4fd82672ac83415cd0d650ea3b8a8cb6fcf38b8ac5476fbfbafcd561cae
Timestamp: 1765368180 Timestamp [UTC]: 2025-12-10 12:03:00 Age [y:d:h:m:s]: 00:344:10:00:02
Block: 1430546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251652 RingCT/type: yes/0
Extra: 017a4ad4fd82672ac83415cd0d650ea3b8a8cb6fcf38b8ac5476fbfbafcd561cae021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1040fd4588555fea2353d8c84f2f0ca46e6e523561c67a64bcb5e066138a4cb3 0.000600000000 1919297 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": 1430556, "vin": [ { "gen": { "height": 1430546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1040fd4588555fea2353d8c84f2f0ca46e6e523561c67a64bcb5e066138a4cb3" } } ], "extra": [ 1, 122, 74, 212, 253, 130, 103, 42, 200, 52, 21, 205, 13, 101, 14, 163, 184, 168, 203, 111, 207, 56, 184, 172, 84, 118, 251, 251, 175, 205, 86, 28, 174, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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: