Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41da20d4d01317581bd41bf31f4a5f8223841fb1a6eae28e8bd24ae2bbb6efdc

Tx prefix hash: 3d60fcfd30815dea1b41990855523d94f4d2163a9c111487684ec5fdd36aabac
Tx public key: 8149c622f328ed6361e1d8b774646ddefc7e1c4869db4678423520424e51221d
Timestamp: 1719263239 Timestamp [UTC]: 2024-06-24 21:07:19 Age [y:d:h:m:s]: 02:148:09:23:48
Block: 1051438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 631040 RingCT/type: yes/0
Extra: 018149c622f328ed6361e1d8b774646ddefc7e1c4869db4678423520424e51221d0211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4acb732b5966c99b4f7bcefe3566dc28cf01eae011fd3a1cc58497e382e9dc26 0.000600000000 1521749 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": 1051448, "vin": [ { "gen": { "height": 1051438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4acb732b5966c99b4f7bcefe3566dc28cf01eae011fd3a1cc58497e382e9dc26" } } ], "extra": [ 1, 129, 73, 198, 34, 243, 40, 237, 99, 97, 225, 216, 183, 116, 100, 109, 222, 252, 126, 28, 72, 105, 219, 70, 120, 66, 53, 32, 66, 78, 81, 34, 29, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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: