Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26015a7cc62e59d99387320a06151877678b20f7a44ee1f368ffaf3f1976a686

Tx prefix hash: 1b769294d963d82502bd7f6bbcb71a27a7310173a269608281bcc98c144a6e79
Tx public key: c3fb8110aa3eb9a082ce7448bf910885ca1ff3fb822a2c7512069bb5ddaf680d
Timestamp: 1574479761 Timestamp [UTC]: 2019-11-23 03:29:21 Age [y:d:h:m:s]: 06:303:20:13:00
Block: 14999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1624980 RingCT/type: yes/0
Extra: 01c3fb8110aa3eb9a082ce7448bf910885ca1ff3fb822a2c7512069bb5ddaf680d021100000004fc8b7a00000000000000000000

1 output(s) for total of 0.547397703116 xmr

stealth address amount amount idx tag
00: 33ae6c5c5cc7df4dc87f38c6a038fe41a1beee34b85149aacc8d5f71c43fa1b2 0.547397703116 19680 of 0 -

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": 15009, "vin": [ { "gen": { "height": 14999 } } ], "vout": [ { "amount": 547397703116, "target": { "key": "33ae6c5c5cc7df4dc87f38c6a038fe41a1beee34b85149aacc8d5f71c43fa1b2" } } ], "extra": [ 1, 195, 251, 129, 16, 170, 62, 185, 160, 130, 206, 116, 72, 191, 145, 8, 133, 202, 31, 243, 251, 130, 42, 44, 117, 18, 6, 155, 181, 221, 175, 104, 13, 2, 17, 0, 0, 0, 4, 252, 139, 122, 0, 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: