Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd75cbc0d96c08b299f46aaab7ca82a3fd452e78f1499e5f6c3065b6e14a5e3

Tx prefix hash: c7775adf919e376402765d14c9d28edc4c145197bbf8239b1f49bb566f56b432
Tx public key: cc7f39dfd6218c5e3af1d0cf01410b041a7857238dc10be0f33357cf7f418465
Timestamp: 1749348337 Timestamp [UTC]: 2025-06-08 02:05:37 Age [y:d:h:m:s]: 00:342:14:28:29
Block: 1300313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234909 RingCT/type: yes/0
Extra: 01cc7f39dfd6218c5e3af1d0cf01410b041a7857238dc10be0f33357cf7f41846502110000000543846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 880d66992a5f90b92c7f6ae23515fe25915b50adbeadf0576778e2d05b5533de 0.000600000000 1787862 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": 1300323, "vin": [ { "gen": { "height": 1300313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "880d66992a5f90b92c7f6ae23515fe25915b50adbeadf0576778e2d05b5533de" } } ], "extra": [ 1, 204, 127, 57, 223, 214, 33, 140, 94, 58, 241, 208, 207, 1, 65, 11, 4, 26, 120, 87, 35, 141, 193, 11, 224, 243, 51, 87, 207, 127, 65, 132, 101, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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: