Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51a1cdcf2cb3e45bc6c76ff52d61c41a15aba17402ebe28fd6e0c4486381a3d0

Tx prefix hash: 4ee4babeb1dbeb355653d9d797bbc1a632c51a2c43cca6e4bf1ec3a5f7792b91
Tx public key: 6725843a2ab8ca2be3c85059f7e7c5a0d22d4b866ff99775eea224bcac1587b4
Timestamp: 1792215168 Timestamp [UTC]: 2026-10-17 05:32:48 Age [y:d:h:m:s]: 00:033:22:47:34
Block: 1656208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 26180 RingCT/type: yes/0
Extra: 016725843a2ab8ca2be3c85059f7e7c5a0d22d4b866ff99775eea224bcac1587b4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5620bd8fd409044b39d2111c49ec6ac7b5b75147dd7cc682038ff7f3742cbb6e 0.000600000000 2146966 of 15 <f2>

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": 1656218, "vin": [ { "gen": { "height": 1656208 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "5620bd8fd409044b39d2111c49ec6ac7b5b75147dd7cc682038ff7f3742cbb6e", "view_tag": "f2" } } } ], "extra": [ 1, 103, 37, 132, 58, 42, 184, 202, 43, 227, 200, 80, 89, 247, 231, 197, 160, 210, 45, 75, 134, 111, 249, 151, 117, 238, 162, 36, 188, 172, 21, 135, 180 ], "rct_signatures": { "type": 0 } }


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