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: 064d874dae936f118163c7244680227d078fcc5d50664ee89f688ffcf48f2627
Tx prefix hash: 9a8529f28615aa2e0078ce627a2ceb2afceba7bd3c338afd027df32826563c0f
Tx public key: 293da041464c7417a0a08f6d555f2376f8953d3be74ea1f50a2d8bb53ef285fa
| Timestamp: 1780690064 | Timestamp [UTC]: 2026-06-05 20:07:44 | Age [y:d:h:m:s]: 00:003:03:11:09 |
| Block: 5632 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2254 | RingCT/type: yes/0 |
| Extra: 01293da041464c7417a0a08f6d555f2376f8953d3be74ea1f50a2d8bb53ef285fa020900000001e49593ff00 | ||
1 output(s) for total of 34.808503795832 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3bb4d1495a39fc5386b697ec2054517551b5d854c9a746162d478cd40ca0daf2 | 34.808503795832 | 7079 of 0 | <5b> |
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": 5692,
"vin": [ {
"gen": {
"height": 5632
}
}
],
"vout": [ {
"amount": 34808503795832,
"target": {
"tagged_key": {
"key": "3bb4d1495a39fc5386b697ec2054517551b5d854c9a746162d478cd40ca0daf2",
"view_tag": "5b"
}
}
}
],
"extra": [ 1, 41, 61, 160, 65, 70, 76, 116, 23, 160, 160, 143, 109, 85, 95, 35, 118, 248, 149, 61, 59, 231, 78, 161, 245, 10, 45, 139, 181, 62, 242, 133, 250, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}