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: 19311e1a903ec6c88731670dede3ff8ad1150f05b4cf2790feb98063ad94dd07
Tx prefix hash: 6dca41e2587086548b0d8a592ca51218fe2e5313e21095d24ef168f8dd2f85d0
Tx public key: c5663d4118ae62b2af37089ed4d8c59752d421dc231bbd39de1d7e6974e89d6b
| Timestamp: 1780753058 | Timestamp [UTC]: 2026-06-06 13:37:38 | Age [y:d:h:m:s]: 00:002:14:01:12 |
| Block: 6505 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1445 | RingCT/type: yes/0 |
| Extra: 01c5663d4118ae62b2af37089ed4d8c59752d421dc231bbd39de1d7e6974e89d6b020900000001e49593ff00 | ||
1 output(s) for total of 34.750591794859 HMNY
| stealth address | amount | amount idx | tag |
| 00: cea131698871d4d522c83716cc0b535f1050cb867f85024ebe00e90f947cd6ce | 34.750591794859 | 8002 of 0 | <d4> |
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": 6565,
"vin": [ {
"gen": {
"height": 6505
}
}
],
"vout": [ {
"amount": 34750591794859,
"target": {
"tagged_key": {
"key": "cea131698871d4d522c83716cc0b535f1050cb867f85024ebe00e90f947cd6ce",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 197, 102, 61, 65, 24, 174, 98, 178, 175, 55, 8, 158, 212, 216, 197, 151, 82, 212, 33, 220, 35, 27, 189, 57, 222, 29, 126, 105, 116, 232, 157, 107, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}