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: d5ce86b47834dfb09a3dba3ccd1b63301de6581d995d31afeb56efed7349ac38
Tx prefix hash: e48a6507768767a7461a85b9874bc19b3474571c4a5c80e9f7e7a8a5c4b57620
Tx public key: 584ca7279456b656bea4cf55b70360cf4011189e3c7f8e2eb4432ff80f53519d
| Timestamp: 1779793617 | Timestamp [UTC]: 2026-05-26 11:06:57 | Age [y:d:h:m:s]: 00:013:12:11:56 |
| Block: 2248 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5638 | RingCT/type: yes/0 |
| Extra: 01584ca7279456b656bea4cf55b70360cf4011189e3c7f8e2eb4432ff80f53519d02090000000326697be300 | ||
1 output(s) for total of 35.033901003780 HMNY
| stealth address | amount | amount idx | tag |
| 00: a37f34e72e06d04b9d45bd0c8321912be756d60af162e7abd32ed71c976a7742 | 35.033901003780 | 2608 of 0 | <2e> |
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": 2308,
"vin": [ {
"gen": {
"height": 2248
}
}
],
"vout": [ {
"amount": 35033901003780,
"target": {
"tagged_key": {
"key": "a37f34e72e06d04b9d45bd0c8321912be756d60af162e7abd32ed71c976a7742",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 88, 76, 167, 39, 148, 86, 182, 86, 190, 164, 207, 85, 183, 3, 96, 207, 64, 17, 24, 158, 60, 127, 142, 46, 180, 67, 47, 248, 15, 83, 81, 157, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}