Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392fd99db37fb6921e37b6bc17af1a5c52a5fde196d33b332db38afeaa68583c

Tx prefix hash: 73d98c35a998bfc379ef5e5312f0f4c0725e7c4284235417fb61353b598d1611
Tx public key: 2df7eb122dcd7aaf96e5cb96766d45fecd32b845e58483a5e8b16ed9faa9c32e
Timestamp: 1696414711 Timestamp [UTC]: 2023-10-04 10:18:31 Age [y:d:h:m:s]: 02:225:01:21:00
Block: 862218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672847 RingCT/type: yes/0
Extra: 012df7eb122dcd7aaf96e5cb96766d45fecd32b845e58483a5e8b16ed9faa9c32e021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.000853323844 xmr

stealth address amount amount idx tag
00: 2603ac9095a5989820af2bec98d183fa32edcb93ef905b98ba1f88a40644c0a2 0.000853323844 1316626 of 0 -

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": 862228, "vin": [ { "gen": { "height": 862218 } } ], "vout": [ { "amount": 853323844, "target": { "key": "2603ac9095a5989820af2bec98d183fa32edcb93ef905b98ba1f88a40644c0a2" } } ], "extra": [ 1, 45, 247, 235, 18, 45, 205, 122, 175, 150, 229, 203, 150, 118, 109, 69, 254, 205, 50, 184, 69, 229, 132, 131, 165, 232, 177, 110, 217, 250, 169, 195, 46, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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: