Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 123d5b297c7c882c39ce3c30bf6d09e97269a2ebede7b89cfcc1108bc3ba4ca5

Tx prefix hash: fea98e121d05192fa3b4d55bc0977010303713b01cb0f07acb5ce7d908628277
Tx public key: a5878519465688982e36b22a7b454301b9f66539b04a2f291ec658f7e845c8cf
Timestamp: 1708430804 Timestamp [UCT]: 2024-02-20 12:06:44 Age [y:d:h:m:s]: 01:082:11:09:41
Block: 961643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319979 RingCT/type: yes/0
Extra: 01a5878519465688982e36b22a7b454301b9f66539b04a2f291ec658f7e845c8cf02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6caf44d94164c2e6d07a297f739e1a2a7f6e11d9df9d83346cdabd703c40618 0.600000000000 1421254 of 15

Check which outputs belong to given Dinastycoin 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 Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-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": 961653, "vin": [ { "gen": { "height": 961643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6caf44d94164c2e6d07a297f739e1a2a7f6e11d9df9d83346cdabd703c40618" } } ], "extra": [ 1, 165, 135, 133, 25, 70, 86, 136, 152, 46, 54, 178, 42, 123, 69, 67, 1, 185, 246, 101, 57, 176, 74, 47, 41, 30, 198, 88, 247, 232, 69, 200, 207, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8