Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a52d16a8b9f391dafd026710bdcd3b8a093c800c723d63e2481834a9cb7a3a43

Tx prefix hash: 6b2c8743ff5064247fed2b6bf4f917cf0457682dc44abb1bb39b63d24ab7eb8c
Tx public key: 13b3ef2778ab067947693a388c1dfb4805aedee4c7a7987b382de583bcb90283
Timestamp: 1733090599 Timestamp [UCT]: 2024-12-01 22:03:19 Age [y:d:h:m:s]: 00:117:14:07:27
Block: 1165989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83837 RingCT/type: yes/0
Extra: 0113b3ef2778ab067947693a388c1dfb4805aedee4c7a7987b382de583bcb90283021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa74d36e5a52903e7e40aecbc0fc819483f8bd7c9b304dbef49bd7a84b346aaf 0.600000000000 1651666 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": 1165999, "vin": [ { "gen": { "height": 1165989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa74d36e5a52903e7e40aecbc0fc819483f8bd7c9b304dbef49bd7a84b346aaf" } } ], "extra": [ 1, 19, 179, 239, 39, 120, 171, 6, 121, 71, 105, 58, 56, 140, 29, 251, 72, 5, 174, 222, 228, 199, 167, 152, 123, 56, 45, 229, 131, 188, 185, 2, 131, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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