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: 6c3722cee09728fb0e17e2e0991654147b42a0fd07a78ef32c186bb9b08c66ab
Tx prefix hash: b1f95f118a4e07631a30259ecc6f2177d69956e854e0ac12cc99c6bb14d6dccb
Tx public key: 54a3c3c09b15293317dd9027f8c8e9ac1862d89e96077de209dad6260d1aa888
| Timestamp: 1780684571 | Timestamp [UTC]: 2026-06-05 18:36:11 | Age [y:d:h:m:s]: 00:003:06:59:46 |
| Block: 5357 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2529 | RingCT/type: yes/0 |
| Extra: 0154a3c3c09b15293317dd9027f8c8e9ac1862d89e96077de209dad6260d1aa888020900000001e49593ff00 | ||
1 output(s) for total of 34.826766389220 HMNY
| stealth address | amount | amount idx | tag |
| 00: 45c8edc9b15db5591b9a8b07b139fa139f1fd6d44f3f18219ec3cc984b042107 | 34.826766389220 | 6790 of 0 | <5a> |
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": 5417,
"vin": [ {
"gen": {
"height": 5357
}
}
],
"vout": [ {
"amount": 34826766389220,
"target": {
"tagged_key": {
"key": "45c8edc9b15db5591b9a8b07b139fa139f1fd6d44f3f18219ec3cc984b042107",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 84, 163, 195, 192, 155, 21, 41, 51, 23, 221, 144, 39, 248, 200, 233, 172, 24, 98, 216, 158, 150, 7, 125, 226, 9, 218, 214, 38, 13, 26, 168, 136, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}