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: 3cf6a73fb111eb14f64fb890ab999b9365130df72951e9b70de6a79bbd130dee
Tx prefix hash: fa50626bf8306f2dd37edb945acb698cd36af3e0d318897302ec7c33733dafbd
Tx public key: 5b30b6022b446c198f3df9f190718d41f27464909fa6ea40ffbc0e01bae77627
| Timestamp: 1780692416 | Timestamp [UTC]: 2026-06-05 20:46:56 | Age [y:d:h:m:s]: 00:003:04:49:01 |
| Block: 5790 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2096 | RingCT/type: yes/0 |
| Extra: 015b30b6022b446c198f3df9f190718d41f27464909fa6ea40ffbc0e01bae77627020900000001e49593ff00 | ||
1 output(s) for total of 34.798015437864 HMNY
| stealth address | amount | amount idx | tag |
| 00: cab1b806364a3afcb55f1cb168e708eb6f0821915ed9f5ed868f7d64d8722e4b | 34.798015437864 | 7245 of 0 | <55> |
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": 5850,
"vin": [ {
"gen": {
"height": 5790
}
}
],
"vout": [ {
"amount": 34798015437864,
"target": {
"tagged_key": {
"key": "cab1b806364a3afcb55f1cb168e708eb6f0821915ed9f5ed868f7d64d8722e4b",
"view_tag": "55"
}
}
}
],
"extra": [ 1, 91, 48, 182, 2, 43, 68, 108, 25, 143, 61, 249, 241, 144, 113, 141, 65, 242, 116, 100, 144, 159, 166, 234, 64, 255, 188, 14, 1, 186, 231, 118, 39, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}