Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 293e901fc212857bed78a5c124e1f411cb87f48d4ba798d3ca90c0b1f0a562bd

Tx prefix hash: 2a785270007cd3223a9bb41810dd123155d9091e04e742fc5b6d26675f4691e5
Tx public key: 03212785b07756aa0d1d2db365b39858bf6a22871957bf542b6438e2cdec1d24
Timestamp: 1709905557 Timestamp [UTC]: 2024-03-08 13:45:57 Age [y:d:h:m:s]: 02:257:11:06:38
Block: 973876 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709175 RingCT/type: yes/0
Extra: 0103212785b07756aa0d1d2db365b39858bf6a22871957bf542b6438e2cdec1d2402110000000952d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c9c8cbb62e59436a8426f860a115e2fb039ec818b9a4f61ea6720ae3066e3a57 0.000600000000 1433819 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": 973886, "vin": [ { "gen": { "height": 973876 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9c8cbb62e59436a8426f860a115e2fb039ec818b9a4f61ea6720ae3066e3a57" } } ], "extra": [ 1, 3, 33, 39, 133, 176, 119, 86, 170, 13, 29, 45, 179, 101, 179, 152, 88, 191, 106, 34, 135, 25, 87, 191, 84, 43, 100, 56, 226, 205, 236, 29, 36, 2, 17, 0, 0, 0, 9, 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: