Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6950ed3e34d3602237590cbf5fceebd754cfa9a2eec0008e1f6a1151387be349

Tx prefix hash: 0f011b2fae5f77b42bc9655dd00b8b9849dcc1891e8cf06dd03ac59157468357
Tx public key: c845839a8708a2b65fc0f10188f2e6ab766b193b9ee8bcfc1eba4fc4425a884d
Timestamp: 1712805396 Timestamp [UTC]: 2024-04-11 03:16:36 Age [y:d:h:m:s]: 02:222:15:56:22
Block: 997885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 684211 RingCT/type: yes/0
Extra: 01c845839a8708a2b65fc0f10188f2e6ab766b193b9ee8bcfc1eba4fc4425a884d02110000000652d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 276bae0405cf76d126b394821d5c753e10a2b8855c4a822c24c090ce37e7a257 0.000600000000 1458319 of 15 -

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": 997895, "vin": [ { "gen": { "height": 997885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "276bae0405cf76d126b394821d5c753e10a2b8855c4a822c24c090ce37e7a257" } } ], "extra": [ 1, 200, 69, 131, 154, 135, 8, 162, 182, 95, 192, 241, 1, 136, 242, 230, 171, 118, 107, 25, 59, 158, 232, 188, 252, 30, 186, 79, 196, 66, 90, 136, 77, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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