Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a1d028d8aeafaf46d851e73a2559e6f7a179160b554e4e2ff37ffd5bd771ca3

Tx prefix hash: d5c5e72f8d8c95a7838fd6f57d7d796ee336b50c6e25ab9d6467b2f020a9a0d4
Tx public key: 6ed79864c3cce8752ca2da2bd7939e4a9cc38ecdfc8b1a22c774fcb7e742d69e
Timestamp: 1787899268 Timestamp [UTC]: 2026-08-28 06:41:08 Age [y:d:h:m:s]: 00:076:06:39:32
Block: 1622707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 53947 RingCT/type: yes/0
Extra: 016ed79864c3cce8752ca2da2bd7939e4a9cc38ecdfc8b1a22c774fcb7e742d69e

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9670448559837abe9c78556413e79c345f6de14611dcf1d1814015a87daf5f18 0.000600000000 2112727 of 15 <d7>

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": 1622717, "vin": [ { "gen": { "height": 1622707 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9670448559837abe9c78556413e79c345f6de14611dcf1d1814015a87daf5f18", "view_tag": "d7" } } } ], "extra": [ 1, 110, 215, 152, 100, 195, 204, 232, 117, 44, 162, 218, 43, 215, 147, 158, 74, 156, 195, 142, 205, 252, 139, 26, 34, 199, 116, 252, 183, 231, 66, 214, 158 ], "rct_signatures": { "type": 0 } }


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