Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57a41e9eee554a27de44dcf40bc1e641494c83a2fd41dadd0e5dab27c0e15efd

Tx prefix hash: b3b6c6b6f9636250b4fa265b1ef60b06f3e791b68da2e881c746da0579796f9c
Tx public key: d7d6dfcab338494c700e1c7e3db40ba0a804d35b974103d32409ccd2b6eefcc5
Timestamp: 1772949882 Timestamp [UTC]: 2026-03-08 06:04:42 Age [y:d:h:m:s]: 00:255:20:07:22
Block: 1493172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188381 RingCT/type: yes/0
Extra: 01d7d6dfcab338494c700e1c7e3db40ba0a804d35b974103d32409ccd2b6eefcc5021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7b703aa74ca4c079a635c5908195e0c86465baaf4e897b0f4e92810105dd8f91 0.000600000000 1982726 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": 1493182, "vin": [ { "gen": { "height": 1493172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b703aa74ca4c079a635c5908195e0c86465baaf4e897b0f4e92810105dd8f91" } } ], "extra": [ 1, 215, 214, 223, 202, 179, 56, 73, 76, 112, 14, 28, 126, 61, 180, 11, 160, 168, 4, 211, 91, 151, 65, 3, 211, 36, 9, 204, 210, 182, 238, 252, 197, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: