Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bfaa3e6bc41e0e5e193f99d91683bde1b67da29bc538aa78f1c228d19e23d2d

Tx prefix hash: 3fca740a64a8b8a668cf36e0b74a99ea25c4200c7b3dc1d5c019638b6ebf2879
Tx public key: f8ae9b4de9e5a10a21dc3c2fd5628d394326449adcecf30c3f856b817c1b2135
Timestamp: 1785962201 Timestamp [UTC]: 2026-08-05 20:36:41 Age [y:d:h:m:s]: 00:105:20:01:41
Block: 1606729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 75286 RingCT/type: yes/0
Extra: 01f8ae9b4de9e5a10a21dc3c2fd5628d394326449adcecf30c3f856b817c1b2135

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: caaf1a37a60c9971c9f07b65ec24e3236344642459d42b32be0f7578f0c5bd7a 0.000600000000 2096749 of 15 <d1>

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": 1606739, "vin": [ { "gen": { "height": 1606729 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "caaf1a37a60c9971c9f07b65ec24e3236344642459d42b32be0f7578f0c5bd7a", "view_tag": "d1" } } } ], "extra": [ 1, 248, 174, 155, 77, 233, 229, 161, 10, 33, 220, 60, 47, 213, 98, 141, 57, 67, 38, 68, 154, 220, 236, 243, 12, 63, 133, 107, 129, 124, 27, 33, 53 ], "rct_signatures": { "type": 0 } }


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