Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7126e3f64e9c338d0b9043d6e10988a880ee524fd0a6efb56bbca84575c83d4

Tx prefix hash: 45121acc9981e321ebb6d9d8a1598adb6eefe806bb67c2652da55b5b49e0c010
Tx public key: 25ab662cd1e13ee16b33cd7f84920dbab8f788cb396cfd4b3475e1176dcf80ee
Timestamp: 1747727749 Timestamp [UTC]: 2025-05-20 07:55:49 Age [y:d:h:m:s]: 01:182:01:24:33
Block: 1286899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394137 RingCT/type: yes/0
Extra: 0125ab662cd1e13ee16b33cd7f84920dbab8f788cb396cfd4b3475e1176dcf80ee0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8f06b4aaf4eb1478a3cc670b6a6356b601735455f616f389bd25c02ecc84062b 0.000600000000 1774366 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": 1286909, "vin": [ { "gen": { "height": 1286899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f06b4aaf4eb1478a3cc670b6a6356b601735455f616f389bd25c02ecc84062b" } } ], "extra": [ 1, 37, 171, 102, 44, 209, 225, 62, 225, 107, 51, 205, 127, 132, 146, 13, 186, 184, 247, 136, 203, 57, 108, 253, 75, 52, 117, 225, 23, 109, 207, 128, 238, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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: