Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3648bd4e7be97265e32e717130114e89bae72d7b464ac68a5c9ca6ab3f257ef8

Tx prefix hash: 682fa402846eaa4fc3e31bd7b2ce918c959678666280747852e3e7fd6bf8be74
Tx public key: c2e9c85933cad8e555a9a7f1503d5bd011d5cc613a3ac702b375807ee35c6998
Timestamp: 1742437228 Timestamp [UTC]: 2025-03-20 02:20:28 Age [y:d:h:m:s]: 01:051:01:24:36
Block: 1243115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287701 RingCT/type: yes/0
Extra: 01c2e9c85933cad8e555a9a7f1503d5bd011d5cc613a3ac702b375807ee35c699802110000000fed95dce7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ba1367bcdacc1981c9f2e4ef33b31048765abf4bf003cbfe8b4b275fba115ed 0.000600000000 1730100 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": 1243125, "vin": [ { "gen": { "height": 1243115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ba1367bcdacc1981c9f2e4ef33b31048765abf4bf003cbfe8b4b275fba115ed" } } ], "extra": [ 1, 194, 233, 200, 89, 51, 202, 216, 229, 85, 169, 167, 241, 80, 61, 91, 208, 17, 213, 204, 97, 58, 58, 199, 2, 179, 117, 128, 126, 227, 92, 105, 152, 2, 17, 0, 0, 0, 15, 237, 149, 220, 231, 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: