Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 059c4eac009d4f9904a9e00e8e20cabbcaa27c78a819170f6bb1646dc8409c66

Tx prefix hash: 9a7e4d23604b1d63d77283dd192f9e99d2c4d99bd716aa7b0afb5d78a423fd8a
Tx public key: d24227a8c1d35f82868db8327257740baf5eea82aeb503e9f1bd38923b07caa1
Timestamp: 1639366713 Timestamp [UTC]: 2021-12-13 03:38:33 Age [y:d:h:m:s]: 04:340:08:51:30
Block: 394353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1286019 RingCT/type: yes/0
Extra: 01d24227a8c1d35f82868db8327257740baf5eea82aeb503e9f1bd38923b07caa1021100000001de12510f000000000000000000

1 output(s) for total of 0.030293731035 xmr

stealth address amount amount idx tag
00: 639e66da514eb6519927a052110c1af897323f2c36182ba0120b291f26c79a40 0.030293731035 791906 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": 394363, "vin": [ { "gen": { "height": 394353 } } ], "vout": [ { "amount": 30293731035, "target": { "key": "639e66da514eb6519927a052110c1af897323f2c36182ba0120b291f26c79a40" } } ], "extra": [ 1, 210, 66, 39, 168, 193, 211, 95, 130, 134, 141, 184, 50, 114, 87, 116, 11, 175, 94, 234, 130, 174, 181, 3, 233, 241, 189, 56, 146, 59, 7, 202, 161, 2, 17, 0, 0, 0, 1, 222, 18, 81, 15, 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: