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: 0655d86d27ee10ce05175f2dc078056d3a84d49b1258ceb6b71b6a34321b45cc
Tx prefix hash: 006a67017eb56074ef7c99b942e67a691d0b52fabde29302d74a1323c7d36f86
Tx public key: 860ec429aae304c4488fba1766fbb451190a381e86fc0a2f3e92f8e389ea0aad
| Timestamp: 1779785054 | Timestamp [UTC]: 2026-05-26 08:44:14 | Age [y:d:h:m:s]: 00:013:14:34:39 |
| Block: 2153 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5733 | RingCT/type: yes/0 |
| Extra: 01860ec429aae304c4488fba1766fbb451190a381e86fc0a2f3e92f8e389ea0aad02090000000126697be300 | ||
1 output(s) for total of 35.040249662001 HMNY
| stealth address | amount | amount idx | tag |
| 00: 725533d6edda87f004d4c1de270d0605c47451026635f8b81d6ba37808cc29a8 | 35.040249662001 | 2485 of 0 | <cd> |
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": 2213,
"vin": [ {
"gen": {
"height": 2153
}
}
],
"vout": [ {
"amount": 35040249662001,
"target": {
"tagged_key": {
"key": "725533d6edda87f004d4c1de270d0605c47451026635f8b81d6ba37808cc29a8",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 134, 14, 196, 41, 170, 227, 4, 196, 72, 143, 186, 23, 102, 251, 180, 81, 25, 10, 56, 30, 134, 252, 10, 47, 62, 146, 248, 227, 137, 234, 10, 173, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}