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: 160e409ffe7d7f669bee9357145cfdbe001e35f90cbf9522d1cd3cbbbc123b99
Tx prefix hash: 467f4c58252489a0283081d6f393dc4d0ed7644c7c45fc7c00a3236780e015e7
Tx public key: 56788648b1d0e2f9181414800917798e23c0a5f883d117024fe7953c10ee0f65
| Timestamp: 1780805388 | Timestamp [UTC]: 2026-06-07 04:09:48 | Age [y:d:h:m:s]: 00:006:06:52:28 |
| Block: 6935 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1810 | RingCT/type: yes/0 |
| Extra: 0156788648b1d0e2f9181414800917798e23c0a5f883d117024fe7953c10ee0f65020900000001e49593ff00 | ||
1 output(s) for total of 34.722102409900 HMNY
| stealth address | amount | amount idx | tag |
| 00: fddd1a8f30a037f779ef63e9d095a64a2996d46d342ee42fea873ce38c22cf74 | 34.722102409900 | 8555 of 0 | <d5> |
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": 6995,
"vin": [ {
"gen": {
"height": 6935
}
}
],
"vout": [ {
"amount": 34722102409900,
"target": {
"tagged_key": {
"key": "fddd1a8f30a037f779ef63e9d095a64a2996d46d342ee42fea873ce38c22cf74",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 86, 120, 134, 72, 177, 208, 226, 249, 24, 20, 20, 128, 9, 23, 121, 142, 35, 192, 165, 248, 131, 209, 23, 2, 79, 231, 149, 60, 16, 238, 15, 101, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}