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: e4bfa45ae082e6dfa21fac797231bf3269243f60ffaa9751d080d18c6629297a
Tx prefix hash: 80fa63016ba3faaefac032b18462f9152b203862504b333b74c97735f74038bc
Tx public key: 8fa5f59c5f2a2f0d6bda8a501d96c72594c4c3529594f5369549557d1630992a
| Timestamp: 1779722526 | Timestamp [UTC]: 2026-05-25 15:22:06 | Age [y:d:h:m:s]: 00:014:10:13:51 |
| Block: 1781 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6105 | RingCT/type: yes/0 |
| Extra: 018fa5f59c5f2a2f0d6bda8a501d96c72594c4c3529594f5369549557d1630992a020900000003ba6d17be00 | ||
1 output(s) for total of 35.065120745803 HMNY
| stealth address | amount | amount idx | tag |
| 00: 07bdd3fd6b47f39c235d31c1a3b9812e8fdb38c7ed10e9b9ab0acd1824724079 | 35.065120745803 | 1968 of 0 | <71> |
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": 1841,
"vin": [ {
"gen": {
"height": 1781
}
}
],
"vout": [ {
"amount": 35065120745803,
"target": {
"tagged_key": {
"key": "07bdd3fd6b47f39c235d31c1a3b9812e8fdb38c7ed10e9b9ab0acd1824724079",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 143, 165, 245, 156, 95, 42, 47, 13, 107, 218, 138, 80, 29, 150, 199, 37, 148, 196, 195, 82, 149, 148, 245, 54, 149, 73, 85, 125, 22, 48, 153, 42, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}