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: ec239d983b161b1632a70cb3d1538ded06aa1a77663198bd50bd5456efedfbb8
Tx prefix hash: 1612a67d4d535cf8a0e7eebec52cd3a078cb4c98bf808e59c3bea11423d3cb78
Tx public key: cecc551139ff9e2efa38eaf6935c05fa7f6ba3caa8185cddb2e040cf429a2bbf
| Timestamp: 1779965640 | Timestamp [UTC]: 2026-05-28 10:54:00 | Age [y:d:h:m:s]: 00:011:14:41:57 |
| Block: 3802 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4084 | RingCT/type: yes/0 |
| Extra: 01cecc551139ff9e2efa38eaf6935c05fa7f6ba3caa8185cddb2e040cf429a2bbf02090000000326697be300 | ||
1 output(s) for total of 34.930213471371 HMNY
| stealth address | amount | amount idx | tag |
| 00: 345431b3b0e89f0375c4604264c16e41135b5fab06a8519580ba646137abb180 | 34.930213471371 | 4625 of 0 | <ea> |
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": 3862,
"vin": [ {
"gen": {
"height": 3802
}
}
],
"vout": [ {
"amount": 34930213471371,
"target": {
"tagged_key": {
"key": "345431b3b0e89f0375c4604264c16e41135b5fab06a8519580ba646137abb180",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 206, 204, 85, 17, 57, 255, 158, 46, 250, 56, 234, 246, 147, 92, 5, 250, 127, 107, 163, 202, 168, 24, 92, 221, 178, 224, 64, 207, 66, 154, 43, 191, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}