Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 969ab1d4b39ca0eb527fc2d79efda26c3ce4341072d443b39fda0f1e7049ea6b

Tx prefix hash: 8a63d218c04a0bdee8e60694c4ff6589d1fb39f59ac97df9808dcdffa615a934
Tx public key: 7a730e6aff10ddd91a589b72ec7bd501e3ee0fdda6cb25c7e573b837f9209213
Timestamp: 1770266278 Timestamp [UTC]: 2026-02-05 04:37:58 Age [y:d:h:m:s]: 00:284:17:24:25
Block: 1470987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 208959 RingCT/type: yes/0
Extra: 017a730e6aff10ddd91a589b72ec7bd501e3ee0fdda6cb25c7e573b837f9209213020813d25390cad81c8e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d17b3f7ede249f8d5cfc945cd2e8d28da9c534eb6138fc3b132d0a3a63bda1f 0.000600000000 1960257 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": 1470997, "vin": [ { "gen": { "height": 1470987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d17b3f7ede249f8d5cfc945cd2e8d28da9c534eb6138fc3b132d0a3a63bda1f" } } ], "extra": [ 1, 122, 115, 14, 106, 255, 16, 221, 217, 26, 88, 155, 114, 236, 123, 213, 1, 227, 238, 15, 221, 166, 203, 37, 199, 229, 115, 184, 55, 249, 32, 146, 19, 2, 8, 19, 210, 83, 144, 202, 216, 28, 142 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: