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: f58d8e069bf4e82aebb258b033f57adef7870a039d1893f109c6d1687a246997
Tx prefix hash: 87456560d7a1dde20c0548f272014e7f57632507d6494dfb0bc3f934c4b7ac1c
Tx public key: 1821c8aba2636bf856369b924908dc2d37e2844b6e964bbbc67aab617d0e4289
| Timestamp: 1780996333 | Timestamp [UTC]: 2026-06-09 09:12:13 | Age [y:d:h:m:s]: 00:000:08:07:50 |
| Block: 8342 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 401 | RingCT/type: yes/0 |
| Extra: 011821c8aba2636bf856369b924908dc2d37e2844b6e964bbbc67aab617d0e4289020900000001e49593ff00 | ||
1 output(s) for total of 34.629045635956 HMNY
| stealth address | amount | amount idx | tag |
| 00: 23b480e64b6ef6e84e6ac1b09b85cc146589aecc9c6f71216562c799631c81fd | 34.629045635956 | 10318 of 0 | <db> |
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": 8402,
"vin": [ {
"gen": {
"height": 8342
}
}
],
"vout": [ {
"amount": 34629045635956,
"target": {
"tagged_key": {
"key": "23b480e64b6ef6e84e6ac1b09b85cc146589aecc9c6f71216562c799631c81fd",
"view_tag": "db"
}
}
}
],
"extra": [ 1, 24, 33, 200, 171, 162, 99, 107, 248, 86, 54, 155, 146, 73, 8, 220, 45, 55, 226, 132, 75, 110, 150, 75, 187, 198, 122, 171, 97, 125, 14, 66, 137, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}