Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9068fda745381b68d567f251acb4e784366c552b058e6a2e32e4bd40abda504c

Tx prefix hash: dfa7ef2852c3dcbdc925feebecc19e5e963f771ee99ce557783625a594a4efce
Tx public key: c2dc57ab245367e06e91e0fe2b87f28064eeebd9d79fffe43f45b23ead4b16ca
Timestamp: 1770859745 Timestamp [UTC]: 2026-02-12 01:29:05 Age [y:d:h:m:s]: 00:276:11:24:40
Block: 1475884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203018 RingCT/type: yes/0
Extra: 01c2dc57ab245367e06e91e0fe2b87f28064eeebd9d79fffe43f45b23ead4b16ca021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9c376fdf7a94389ef9ee62989eba733f1bf08c99607989db15a7cadee0721fc9 0.000600000000 1965188 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": 1475894, "vin": [ { "gen": { "height": 1475884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c376fdf7a94389ef9ee62989eba733f1bf08c99607989db15a7cadee0721fc9" } } ], "extra": [ 1, 194, 220, 87, 171, 36, 83, 103, 224, 110, 145, 224, 254, 43, 135, 242, 128, 100, 238, 235, 217, 215, 159, 255, 228, 63, 69, 178, 62, 173, 75, 22, 202, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: