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: 0f46a7a3949c94e4a44654e181215dafd597c9328e4e9fc0b730e1b93b22718f
Tx prefix hash: 5517f4e07806833b59dbbcbb9384ed25e6e3d4be33dbde27b70c199e8f4b9ce6
Tx public key: 50e26b6bb06fa3d076c9c190ab93b89bb805cf46d0f6fcf7cd440a345cb57deb
| Timestamp: 1780043811 | Timestamp [UTC]: 2026-05-29 08:36:51 | Age [y:d:h:m:s]: 00:010:18:03:45 |
| Block: 4320 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3577 | RingCT/type: yes/0 |
| Extra: 0150e26b6bb06fa3d076c9c190ab93b89bb805cf46d0f6fcf7cd440a345cb57deb02090000000426697be300 | ||
1 output(s) for total of 34.895719200402 HMNY
| stealth address | amount | amount idx | tag |
| 00: b33febecc188e3ae80074a18fb955ad91a357a2ec0ebf58933cf97d4c434f637 | 34.895719200402 | 5398 of 0 | <80> |
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": 4380,
"vin": [ {
"gen": {
"height": 4320
}
}
],
"vout": [ {
"amount": 34895719200402,
"target": {
"tagged_key": {
"key": "b33febecc188e3ae80074a18fb955ad91a357a2ec0ebf58933cf97d4c434f637",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 80, 226, 107, 107, 176, 111, 163, 208, 118, 201, 193, 144, 171, 147, 184, 155, 184, 5, 207, 70, 208, 246, 252, 247, 205, 68, 10, 52, 92, 181, 125, 235, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}