Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c1842a6cb918aa18dc122d81ea563617c7bd9d2b3c11daccedf567745f5a1ad

Tx prefix hash: c28c76c3d9a79b444c33fdfc72fbabe97f220a86443e5ed037edc642cda0fa00
Tx public key: b2fe647b3e6d21c79a7810dd654282aedad4f2e8827c4f97ee4fd7b33712eb69
Timestamp: 1705641205 Timestamp [UTC]: 2024-01-19 05:13:25 Age [y:d:h:m:s]: 02:217:07:45:59
Block: 938492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680714 RingCT/type: yes/0
Extra: 01b2fe647b3e6d21c79a7810dd654282aedad4f2e8827c4f97ee4fd7b33712eb690211000000060011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5b9e30231635fab9cfc72e04bcb148c79c01a209896a1c192dfc6d40d705a09f 0.000600000000 1396562 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": 938502, "vin": [ { "gen": { "height": 938492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b9e30231635fab9cfc72e04bcb148c79c01a209896a1c192dfc6d40d705a09f" } } ], "extra": [ 1, 178, 254, 100, 123, 62, 109, 33, 199, 154, 120, 16, 221, 101, 66, 130, 174, 218, 212, 242, 232, 130, 124, 79, 151, 238, 79, 215, 179, 55, 18, 235, 105, 2, 17, 0, 0, 0, 6, 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: