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: b254f7410d76b1bf12df3ca88ae0c3ea0e968d5146f2409ea3dcdf0adb60246f
Tx prefix hash: 95c97e428b38433dca49d86357aea7eec3d5cde4adde3943d6c246572c0bbd06
Tx public key: 5ad0473b460296d5f37ba68e393df93631d891fa8354f6de0a8ccf4b58b46d05
| Timestamp: 1780384067 | Timestamp [UTC]: 2026-06-02 07:07:47 | Age [y:d:h:m:s]: 00:011:03:54:29 |
| Block: 5168 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3577 | RingCT/type: yes/0 |
| Extra: 015ad0473b460296d5f37ba68e393df93631d891fa8354f6de0a8ccf4b58b46d0502090000000326697be300 | ||
1 output(s) for total of 34.839323326791 HMNY
| stealth address | amount | amount idx | tag |
| 00: 307a37e2078dcf9187a138c641093a70b063fb0fd5e4a7a76b7bc1fac23e1f90 | 34.839323326791 | 6547 of 0 | <b1> |
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": 5228,
"vin": [ {
"gen": {
"height": 5168
}
}
],
"vout": [ {
"amount": 34839323326791,
"target": {
"tagged_key": {
"key": "307a37e2078dcf9187a138c641093a70b063fb0fd5e4a7a76b7bc1fac23e1f90",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 90, 208, 71, 59, 70, 2, 150, 213, 243, 123, 166, 142, 57, 61, 249, 54, 49, 216, 145, 250, 131, 84, 246, 222, 10, 140, 207, 75, 88, 180, 109, 5, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}