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: 6e39373fe45061648ab2097b4d242b0ba813712cb83184e64e4472e62a75c930
Tx prefix hash: b16590574b41ecc411e95aefe858475453581a578db44e870a746521573f24a2
Tx public key: 45743eb1cf3b805efa0a01caa42903f504d60cbc9b3e6fa13bada72017586742
| Timestamp: 1779999206 | Timestamp [UTC]: 2026-05-28 20:13:26 | Age [y:d:h:m:s]: 00:011:03:05:27 |
| Block: 4046 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3840 | RingCT/type: yes/0 |
| Extra: 0145743eb1cf3b805efa0a01caa42903f504d60cbc9b3e6fa13bada7201758674202090000000226697be300 | ||
1 output(s) for total of 34.913960958910 HMNY
| stealth address | amount | amount idx | tag |
| 00: d2d12bef7993d3c3f0e7053bf53686862facddd0fe8dc917d7dccc13453832a7 | 34.913960958910 | 5011 of 0 | <45> |
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": 4106,
"vin": [ {
"gen": {
"height": 4046
}
}
],
"vout": [ {
"amount": 34913960958910,
"target": {
"tagged_key": {
"key": "d2d12bef7993d3c3f0e7053bf53686862facddd0fe8dc917d7dccc13453832a7",
"view_tag": "45"
}
}
}
],
"extra": [ 1, 69, 116, 62, 177, 207, 59, 128, 94, 250, 10, 1, 202, 164, 41, 3, 245, 4, 214, 12, 188, 155, 62, 111, 161, 59, 173, 167, 32, 23, 88, 103, 66, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}