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: d9047714581a3c04ff6b19a08c8901768553aa92950b2bcfa78740d884bf2526
Tx prefix hash: 45df9d59ed5d1518d1da3e7724143f5c2ce1e30b3f8893b64a3dc71fa0b9dc87
Tx public key: 0890315fea8c286b09128accd403672cdb4222acec364245ac4bda83bfc47f2d
| Timestamp: 1780688216 | Timestamp [UTC]: 2026-06-05 19:36:56 | Age [y:d:h:m:s]: 00:003:07:12:52 |
| Block: 5517 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2392 | RingCT/type: yes/0 |
| Extra: 010890315fea8c286b09128accd403672cdb4222acec364245ac4bda83bfc47f2d020900000002e49593ff00 | ||
1 output(s) for total of 34.816139715028 HMNY
| stealth address | amount | amount idx | tag |
| 00: b1d7378e4f3ce1736f87f5e1638c8cbdae16440f13c181d94394261c8572e135 | 34.816139715028 | 6958 of 0 | <4e> |
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": 5577,
"vin": [ {
"gen": {
"height": 5517
}
}
],
"vout": [ {
"amount": 34816139715028,
"target": {
"tagged_key": {
"key": "b1d7378e4f3ce1736f87f5e1638c8cbdae16440f13c181d94394261c8572e135",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 8, 144, 49, 95, 234, 140, 40, 107, 9, 18, 138, 204, 212, 3, 103, 44, 219, 66, 34, 172, 236, 54, 66, 69, 172, 75, 218, 131, 191, 196, 127, 45, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}