Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccbc54bbb0d380f4119cef39726c5d1c830324d8df212e1570c12f5279dbf4e3

Tx prefix hash: 62d83a203b5c6e6898a1210d6b444f878c2f985f3db28fd5f1683ec41206f795
Tx public key: 863640f9d3d0e021ebff852e3b8aff7a25aea8d7dcf981689e83d76d26e9c3d5
Timestamp: 1781403930 Timestamp [UTC]: 2026-06-14 02:25:30 Age [y:d:h:m:s]: 00:160:12:21:52
Block: 1558769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 124708 RingCT/type: yes/0
Extra: 01863640f9d3d0e021ebff852e3b8aff7a25aea8d7dcf981689e83d76d26e9c3d5

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 068046727d20c4d8f6e06752670fb66dd0ea1d0549b6778dc2c4bd44ae2f1d9a 0.000600000000 2048747 of 15 <d9>

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": 1558779, "vin": [ { "gen": { "height": 1558769 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "068046727d20c4d8f6e06752670fb66dd0ea1d0549b6778dc2c4bd44ae2f1d9a", "view_tag": "d9" } } } ], "extra": [ 1, 134, 54, 64, 249, 211, 208, 224, 33, 235, 255, 133, 46, 59, 138, 255, 122, 37, 174, 168, 215, 220, 249, 129, 104, 158, 131, 215, 109, 38, 233, 195, 213 ], "rct_signatures": { "type": 0 } }


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