Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0ae04c97b3b5abc384183b2ae5f7c67f06fab508e58db192e2b16068e6efc98

Tx prefix hash: d004c32c21b0312b846539f8e3a2ee672645642a1f45f3ff61faf650db8b90c7
Tx public key: 2df2af4c82b2a3244aaee5281bb5ae868f0775a7eeadf00ca2c2d2a9e6eddd42
Timestamp: 1746875923 Timestamp [UTC]: 2025-05-10 11:18:43 Age [y:d:h:m:s]: 01:062:13:06:52
Block: 1279836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300384 RingCT/type: yes/0
Extra: 012df2af4c82b2a3244aaee5281bb5ae868f0775a7eeadf00ca2c2d2a9e6eddd420211000000031f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ae3a84d29eba54a30d68f7f7b5819611413239b115d97741dd75b89c11e7686 0.000600000000 1767219 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": 1279846, "vin": [ { "gen": { "height": 1279836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ae3a84d29eba54a30d68f7f7b5819611413239b115d97741dd75b89c11e7686" } } ], "extra": [ 1, 45, 242, 175, 76, 130, 178, 163, 36, 74, 174, 229, 40, 27, 181, 174, 134, 143, 7, 117, 167, 238, 173, 240, 12, 162, 194, 210, 169, 230, 237, 221, 66, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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: