For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 980a73c0391e62e8c8044e1db2c9542379f660f8af47f09de12bb68fed13f0fa
Tx prefix hash: b9d337743be9fdb1d596c4e6d585c05eeaa2527161eeaa01ee9bdd2260b2ea9d
Tx public key: d6a6640b70e9c5325e9fef70313b923f9a02d65bc62c4ae9d72e950eb31d81f1
| Timestamp: 1779469084 | Timestamp [UTC]: 2026-05-22 16:58:04 | Age [y:d:h:m:s]: 00:017:11:34:58 |
| Block: 543 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7466 | RingCT/type: yes/0 |
| Extra: 01d6a6640b70e9c5325e9fef70313b923f9a02d65bc62c4ae9d72e950eb31d81f102090000000393369e7d00 | ||
1 output(s) for total of 35.148017844424 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc921484c5212cf66797e96f2207626f13695738a270be6c3fab23d62710f0c2 | 35.148017844424 | 547 of 0 | <16> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 603,
"vin": [ {
"gen": {
"height": 543
}
}
],
"vout": [ {
"amount": 35148017844424,
"target": {
"tagged_key": {
"key": "dc921484c5212cf66797e96f2207626f13695738a270be6c3fab23d62710f0c2",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 214, 166, 100, 11, 112, 233, 197, 50, 94, 159, 239, 112, 49, 59, 146, 63, 154, 2, 214, 91, 198, 44, 74, 233, 215, 46, 149, 14, 179, 29, 129, 241, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}