Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f28df85c640a212c92f054baa0a1e3983b93f9cbfee35a82bfb0b3454855d03e

Tx prefix hash: 197082c800fbfb0a0a101737c409dfe0455eed7da8e62f4593e4bc23bf7d8663
Tx public key: 7f8da8ade120356854d1a39c255ef40066db3233b3452a96d125273725a4c040
Timestamp: 1734214846 Timestamp [UTC]: 2024-12-14 22:20:46 Age [y:d:h:m:s]: 01:339:13:57:17
Block: 1175306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506573 RingCT/type: yes/0
Extra: 017f8da8ade120356854d1a39c255ef40066db3233b3452a96d125273725a4c0400211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a7189e0e73b7b9a12691ef1fba603e759974ff802841c04b0281a9a5a316cbc0 0.000600000000 1661569 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": 1175316, "vin": [ { "gen": { "height": 1175306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7189e0e73b7b9a12691ef1fba603e759974ff802841c04b0281a9a5a316cbc0" } } ], "extra": [ 1, 127, 141, 168, 173, 225, 32, 53, 104, 84, 209, 163, 156, 37, 94, 244, 0, 102, 219, 50, 51, 179, 69, 42, 150, 209, 37, 39, 55, 37, 164, 192, 64, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: