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: 095929631caa03eb683efb8bab674bd2610e831b2ac4301bfb030452d6d58036
Tx prefix hash: 9926d52ba534d2c8aaffe528ae5b4c05368f703fb3aa2c13c759d59ce3867397
Tx public key: b6bcdcfe3b3fe483343df08120fc4540fd4acf6dbc00855d6ab6bdf581bf688c
| Timestamp: 1780827222 | Timestamp [UTC]: 2026-06-07 10:13:42 | Age [y:d:h:m:s]: 00:001:14:33:05 |
| Block: 7286 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 600 | RingCT/type: yes/0 |
| Extra: 01b6bcdcfe3b3fe483343df08120fc4540fd4acf6dbc00855d6ab6bdf581bf688c020900000004e49593ff00 | ||
1 output(s) for total of 34.698864436028 HMNY
| stealth address | amount | amount idx | tag |
| 00: da16ac8f4180454dc9b2c29c291e4f508b1eade20fc964dab11ef2449bb0d668 | 34.698864436028 | 8970 of 0 | <bd> |
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": 7346,
"vin": [ {
"gen": {
"height": 7286
}
}
],
"vout": [ {
"amount": 34698864436028,
"target": {
"tagged_key": {
"key": "da16ac8f4180454dc9b2c29c291e4f508b1eade20fc964dab11ef2449bb0d668",
"view_tag": "bd"
}
}
}
],
"extra": [ 1, 182, 188, 220, 254, 59, 63, 228, 131, 52, 61, 240, 129, 32, 252, 69, 64, 253, 74, 207, 109, 188, 0, 133, 93, 106, 182, 189, 245, 129, 191, 104, 140, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}