Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 763a292eff999281b6ba4d2caa93a6c8678affcbf9d7cd2ed4ba7e17ae699828

Tx prefix hash: 793078ec8fb3d5e41b1584c333aa468d815a30c5dc05b14bc12393b3728620f7
Tx public key: 0ea9d1642fe77edbd17c30935aeb09e6979cc53286c5045b5b7ce0c7bdd93e47
Timestamp: 1705850487 Timestamp [UTC]: 2024-01-21 15:21:27 Age [y:d:h:m:s]: 02:305:19:19:56
Block: 940216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 743278 RingCT/type: yes/0
Extra: 010ea9d1642fe77edbd17c30935aeb09e6979cc53286c5045b5b7ce0c7bdd93e4702110000000179bda3be000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06a8d5dbaf41f5f636789190a6d45e1c4f21c57e3c030108b1e942f3208d3396 0.000600000000 1398350 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": 940226, "vin": [ { "gen": { "height": 940216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06a8d5dbaf41f5f636789190a6d45e1c4f21c57e3c030108b1e942f3208d3396" } } ], "extra": [ 1, 14, 169, 209, 100, 47, 231, 126, 219, 209, 124, 48, 147, 90, 235, 9, 230, 151, 156, 197, 50, 134, 197, 4, 91, 91, 124, 224, 199, 189, 217, 62, 71, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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: