Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c522fc89f1789e0c35f70a5ae4037702d755981ad0426fb8320ff4159d783ed

Tx prefix hash: 0e1e6c9a982a36510e815e4de43ac285e612647c19723fdb8ce027b7c3a6fadb
Tx public key: 80e7d2ad4f4b49047fd026b50d58e38cb9914bc108dff2ae43017ef08c846d56
Timestamp: 1695648735 Timestamp [UCT]: 2023-09-25 13:32:15 Age [y:d:h:m:s]: 01:205:19:47:38
Block: 855866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408180 RingCT/type: yes/0
Extra: 0180e7d2ad4f4b49047fd026b50d58e38cb9914bc108dff2ae43017ef08c846d5602110000000475e3f0e9000000000000000000

1 output(s) for total of 0.895696141000 dcy

stealth address amount amount idx
00: af9141d345b603e10f81f50ba0f9fdf24391e7df1f0d7a10148554e405cf86ed 0.895696141000 1309914 of 0

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": 855876, "vin": [ { "gen": { "height": 855866 } } ], "vout": [ { "amount": 895696141, "target": { "key": "af9141d345b603e10f81f50ba0f9fdf24391e7df1f0d7a10148554e405cf86ed" } } ], "extra": [ 1, 128, 231, 210, 173, 79, 75, 73, 4, 127, 208, 38, 181, 13, 88, 227, 140, 185, 145, 75, 193, 8, 223, 242, 174, 67, 1, 126, 240, 140, 132, 109, 86, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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