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: a551b039ca7b8c9ce0c9ef2b2a982ef9708f6d0eb91c8e2b536f65da4df3700c
Tx prefix hash: 8f1f5873494e3c593f77791b0ebe0e2213473eaf051cbbe1679991167faf5d1d
Tx public key: 7058b5377315c4e21ca0702af70e51e4e5df9a83da399c0eecb7003bbb5126d4
| Timestamp: 1780984730 | Timestamp [UTC]: 2026-06-09 05:58:50 | Age [y:d:h:m:s]: 00:000:10:00:54 |
| Block: 8121 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 569 | RingCT/type: yes/0 |
| Extra: 017058b5377315c4e21ca0702af70e51e4e5df9a83da399c0eecb7003bbb5126d4020900000001e49593ff00 | ||
1 output(s) for total of 34.643645702292 HMNY
| stealth address | amount | amount idx | tag |
| 00: ffe70bd20944c62feb4064a0a1f7003561445de090822e2b6f38c72347f9f13a | 34.643645702292 | 10057 of 0 | <3b> |
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": 8181,
"vin": [ {
"gen": {
"height": 8121
}
}
],
"vout": [ {
"amount": 34643645702292,
"target": {
"tagged_key": {
"key": "ffe70bd20944c62feb4064a0a1f7003561445de090822e2b6f38c72347f9f13a",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 112, 88, 181, 55, 115, 21, 196, 226, 28, 160, 112, 42, 247, 14, 81, 228, 229, 223, 154, 131, 218, 57, 156, 14, 236, 183, 0, 59, 187, 81, 38, 212, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}