Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e00c2f75275306449560fa3872fbc6a7e0529f3857eebbec1d0c27cf88e7c2f

Tx prefix hash: 0105d4d86bc3005edad9ea6fcf69c061ca99d9b647638929986292e53d4903e3
Tx public key: 4beb795b35de253911f7bd5606b01944e0d59571e7ef86677510029c9d453f72
Timestamp: 1771501591 Timestamp [UTC]: 2026-02-19 11:46:31 Age [y:d:h:m:s]: 00:271:19:13:40
Block: 1481180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199777 RingCT/type: yes/0
Extra: 014beb795b35de253911f7bd5606b01944e0d59571e7ef86677510029c9d453f72021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 82c3c4aa220730ad82006b1f9a131afc5ea5a1fe5c2cb1e72208e6b96d1b8caf 0.000600000000 1970556 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": 1481190, "vin": [ { "gen": { "height": 1481180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82c3c4aa220730ad82006b1f9a131afc5ea5a1fe5c2cb1e72208e6b96d1b8caf" } } ], "extra": [ 1, 75, 235, 121, 91, 53, 222, 37, 57, 17, 247, 189, 86, 6, 176, 25, 68, 224, 213, 149, 113, 231, 239, 134, 103, 117, 16, 2, 156, 157, 69, 63, 114, 2, 17, 0, 0, 0, 1, 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: