Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68f18bfb3a4fcc9c03b593f08148feba9d8d57b9f611901dfdf0d152ea7beb0e

Tx prefix hash: 558e56a82706505a64c53193aefc8532e7998d7ffe1793e466aef44b7c8be3dc
Tx public key: 81954c77f8cce4c9ab45802d2d2b7b42f2fa2732e8e281244245f278c481cac5
Timestamp: 1781690421 Timestamp [UTC]: 2026-06-17 10:00:21 Age [y:d:h:m:s]: 00:155:14:24:32
Block: 1561417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 120847 RingCT/type: yes/0
Extra: 0181954c77f8cce4c9ab45802d2d2b7b42f2fa2732e8e281244245f278c481cac50208d46ac48624edd8bb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b963013c6090a326841b6f44f60a1ba1077a5330bcfdac9be5e3fae2060cf8d1 0.000600000000 2051395 of 15 <57>

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": 1561427, "vin": [ { "gen": { "height": 1561417 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b963013c6090a326841b6f44f60a1ba1077a5330bcfdac9be5e3fae2060cf8d1", "view_tag": "57" } } } ], "extra": [ 1, 129, 149, 76, 119, 248, 204, 228, 201, 171, 69, 128, 45, 45, 43, 123, 66, 242, 250, 39, 50, 232, 226, 129, 36, 66, 69, 242, 120, 196, 129, 202, 197, 2, 8, 212, 106, 196, 134, 36, 237, 216, 187 ], "rct_signatures": { "type": 0 } }


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