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: 3c70d193794164d1fd2a1334838e15d872c12b2d5c624a4f466b85b1f87df4d3
Tx prefix hash: 1cef9629d6953f831f1edeb4a91ef24b70868b879078f8c8db07073a376d817f
Tx public key: 994ff385347a8a5a54d8b6d9e8fe2e84bbca7d57d6d0461ad985628aab5dc236
| Timestamp: 1780703870 | Timestamp [UTC]: 2026-06-05 23:57:50 | Age [y:d:h:m:s]: 00:003:01:38:07 |
| Block: 6085 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1801 | RingCT/type: yes/0 |
| Extra: 01994ff385347a8a5a54d8b6d9e8fe2e84bbca7d57d6d0461ad985628aab5dc236020900000001e49593ff00 | ||
1 output(s) for total of 34.778441202195 HMNY
| stealth address | amount | amount idx | tag |
| 00: 289d74b7430ace1e2592b68a5222edf7df8a43fcfbde073eff2c2f68168c3aa7 | 34.778441202195 | 7556 of 0 | <50> |
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": 6145,
"vin": [ {
"gen": {
"height": 6085
}
}
],
"vout": [ {
"amount": 34778441202195,
"target": {
"tagged_key": {
"key": "289d74b7430ace1e2592b68a5222edf7df8a43fcfbde073eff2c2f68168c3aa7",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 153, 79, 243, 133, 52, 122, 138, 90, 84, 216, 182, 217, 232, 254, 46, 132, 187, 202, 125, 87, 214, 208, 70, 26, 217, 133, 98, 138, 171, 93, 194, 54, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}