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: 7966df01a3a57847bfe4971ff685432b9b114f27a219b3818e4434ebe3fc5562
Tx prefix hash: 187cb55e7d637da384e40769107a281fb85803e8d24f1aaf36ae6cd39658012f
Tx public key: 3b19011bfe9a1e8aadde64a1c685ab43b97b012d1e347dbff193da9c06cd1453
| Timestamp: 1780905097 | Timestamp [UTC]: 2026-06-08 07:51:37 | Age [y:d:h:m:s]: 00:000:13:20:30 |
| Block: 7856 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 30 | RingCT/type: yes/0 |
| Extra: 013b19011bfe9a1e8aadde64a1c685ab43b97b012d1e347dbff193da9c06cd14530209000000014a728a4c00 | ||
1 output(s) for total of 34.661160685295 HMNY
| stealth address | amount | amount idx | tag |
| 00: b930ebdec59cc54319fa3324706f520957b25c8156d2bb5dfda4fb96c5b792f3 | 34.661160685295 | 9740 of 0 | <f4> |
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": 7916,
"vin": [ {
"gen": {
"height": 7856
}
}
],
"vout": [ {
"amount": 34661160685295,
"target": {
"tagged_key": {
"key": "b930ebdec59cc54319fa3324706f520957b25c8156d2bb5dfda4fb96c5b792f3",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 59, 25, 1, 27, 254, 154, 30, 138, 173, 222, 100, 161, 198, 133, 171, 67, 185, 123, 1, 45, 30, 52, 125, 191, 241, 147, 218, 156, 6, 205, 20, 83, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}