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: 6f747b12980ac0f7c47835b37f19bab9dfc988da58575380ed7c074c4a737b5b
Tx prefix hash: 4cf1ffcebf019dd0a36d0b72d79d15161281220b4a7d8cf95f37c40eb72682a8
Tx public key: d9b92b7d7da26491ad5b8ce84eab80081a8ece79e70a17df409b4284033004fe
| Timestamp: 1779923975 | Timestamp [UTC]: 2026-05-27 23:19:35 | Age [y:d:h:m:s]: 00:012:02:16:22 |
| Block: 3369 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4517 | RingCT/type: yes/0 |
| Extra: 01d9b92b7d7da26491ad5b8ce84eab80081a8ece79e70a17df409b4284033004fe02090000000126697be300 | ||
1 output(s) for total of 34.959073647899 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3abdaa62d157e1407c8e6de36ff1627fa1a7c379d8bffaf82271e2e3601df571 | 34.959073647899 | 4062 of 0 | <8c> |
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": 3429,
"vin": [ {
"gen": {
"height": 3369
}
}
],
"vout": [ {
"amount": 34959073647899,
"target": {
"tagged_key": {
"key": "3abdaa62d157e1407c8e6de36ff1627fa1a7c379d8bffaf82271e2e3601df571",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 217, 185, 43, 125, 125, 162, 100, 145, 173, 91, 140, 232, 78, 171, 128, 8, 26, 142, 206, 121, 231, 10, 23, 223, 64, 155, 66, 132, 3, 48, 4, 254, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}