Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50de64b9e4f7626f40e5693ad857b26fcd8f3001b05ab258d4e7bc2550127e68

Tx prefix hash: e8ff8aa5865f3b7de62a100c87dcabc0e117d70e313a3d1f64f67426da544479
Tx public key: c66745f372878e536491c4ac3968683378349e6f6b3b86dfdf36aa3ccfe9752b
Timestamp: 1771294824 Timestamp [UTC]: 2026-02-17 02:20:24 Age [y:d:h:m:s]: 00:273:08:15:59
Block: 1479458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200869 RingCT/type: yes/0
Extra: 01c66745f372878e536491c4ac3968683378349e6f6b3b86dfdf36aa3ccfe9752b021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b3627938f1313cd0a321946660b6834da8a584437a081e79c9aa77996a3feb4a 0.000600000000 1968806 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": 1479468, "vin": [ { "gen": { "height": 1479458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3627938f1313cd0a321946660b6834da8a584437a081e79c9aa77996a3feb4a" } } ], "extra": [ 1, 198, 103, 69, 243, 114, 135, 142, 83, 100, 145, 196, 172, 57, 104, 104, 51, 120, 52, 158, 111, 107, 59, 134, 223, 223, 54, 170, 60, 207, 233, 117, 43, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: