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: 3180540f644f1787a538ba9633baa2a450c9a07e35f12f46c987dff59d2ec77b
Tx prefix hash: a931ee8f6ab7daead7a99742f5730ee68fd377142ba54d0e22c308b541608d83
Tx public key: df9ce88ad24f40b77ef161da123bcf772b499d4d4e75614eb05e0fade9267308
| Timestamp: 1781003111 | Timestamp [UTC]: 2026-06-09 11:05:11 | Age [y:d:h:m:s]: 00:007:22:09:55 |
| Block: 8488 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 257 | RingCT/type: yes/0 |
| Extra: 01df9ce88ad24f40b77ef161da123bcf772b499d4d4e75614eb05e0fade9267308020900000004e49593ff00 | ||
1 output(s) for total of 34.619403718553 HMNY
| stealth address | amount | amount idx | tag |
| 00: b01abfcefb40607f67c33dfcd9f34f8c6bf9b11aa1ce02c3d31f9b2a11ab647c | 34.619403718553 | 10486 of 0 | <0d> |
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": 8548,
"vin": [ {
"gen": {
"height": 8488
}
}
],
"vout": [ {
"amount": 34619403718553,
"target": {
"tagged_key": {
"key": "b01abfcefb40607f67c33dfcd9f34f8c6bf9b11aa1ce02c3d31f9b2a11ab647c",
"view_tag": "0d"
}
}
}
],
"extra": [ 1, 223, 156, 232, 138, 210, 79, 64, 183, 126, 241, 97, 218, 18, 59, 207, 119, 43, 73, 157, 77, 78, 117, 97, 78, 176, 94, 15, 173, 233, 38, 115, 8, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}