Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4692348fa2c4066a13d319e9ea6bf55fa4adfd1e1d11f2ffe3f8a302eb7b4f1

Tx prefix hash: a8a8f172e1d159b6bafe953d0caf68fb8a1851499f52605a8e58620e201f7217
Tx public key: 6fbd0600cd0276daec8b525c2f59c2087fd04a01eb38c7d3b30d3a582a1a0f9b
Timestamp: 1785097677 Timestamp [UTC]: 2026-07-26 20:27:57 Age [y:d:h:m:s]: 00:113:05:41:45
Block: 1598253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 81818 RingCT/type: yes/0
Extra: 016fbd0600cd0276daec8b525c2f59c2087fd04a01eb38c7d3b30d3a582a1a0f9b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6bb6d5a3934306702b56e56b92bcf2852157f22dcd0b4c00e3c1bcd71ae31fc6 0.000600000000 2088271 of 15 <5a>

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": 1598263, "vin": [ { "gen": { "height": 1598253 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "6bb6d5a3934306702b56e56b92bcf2852157f22dcd0b4c00e3c1bcd71ae31fc6", "view_tag": "5a" } } } ], "extra": [ 1, 111, 189, 6, 0, 205, 2, 118, 218, 236, 139, 82, 92, 47, 89, 194, 8, 127, 208, 74, 1, 235, 56, 199, 211, 179, 13, 58, 88, 42, 26, 15, 155 ], "rct_signatures": { "type": 0 } }


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