Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0da9b6f219076ff017e3f3e077e89a4f59cdc35af2dcfaff5b07ec1a6db2c2f

Tx prefix hash: f9e68b2c68a035d2d27f06f0c7624e6af20d9e9fa9da33a96583160f46fde225
Tx public key: 7c688f59d147bf978afbf0854fbc99baa8aa15f6183a4fc3e9f2b477f547996d
Timestamp: 1786451431 Timestamp [UTC]: 2026-08-11 12:30:31 Age [y:d:h:m:s]: 00:099:20:11:34
Block: 1610913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 70849 RingCT/type: yes/0
Extra: 017c688f59d147bf978afbf0854fbc99baa8aa15f6183a4fc3e9f2b477f547996d

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 54ce705a3dcc18b70ad060f40eaf7df3cbe7cd069683850b39479862bbc4e39a 0.000600000000 2100933 of 15 <6f>

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": 1610923, "vin": [ { "gen": { "height": 1610913 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "54ce705a3dcc18b70ad060f40eaf7df3cbe7cd069683850b39479862bbc4e39a", "view_tag": "6f" } } } ], "extra": [ 1, 124, 104, 143, 89, 209, 71, 191, 151, 138, 251, 240, 133, 79, 188, 153, 186, 168, 170, 21, 246, 24, 58, 79, 195, 233, 242, 180, 119, 245, 71, 153, 109 ], "rct_signatures": { "type": 0 } }


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