Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0c0d42d343c25a324741fa992f1474be70b97869af5f8aac0dd9c98d44708c6

Tx prefix hash: 40f1c5f5599e83c32929a5c73924cb9d6bd42568feef40e2abdb06fde81f61d8
Tx public key: 5b5c27e3cd44eb423dc3f7d92f1e7d7114d1f8b579e69e3f9da0ca1b989fca1a
Timestamp: 1705405713 Timestamp [UCT]: 2024-01-16 11:48:33 Age [y:d:h:m:s]: 01:295:12:44:49
Block: 936542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470022 RingCT/type: yes/0
Extra: 015b5c27e3cd44eb423dc3f7d92f1e7d7114d1f8b579e69e3f9da0ca1b989fca1a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e94acb7f0ff3293ef30760bc4d4a225f693aed5e51f4ad9b9820b6557e5adfb9 0.600000000000 1394570 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": 936552, "vin": [ { "gen": { "height": 936542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e94acb7f0ff3293ef30760bc4d4a225f693aed5e51f4ad9b9820b6557e5adfb9" } } ], "extra": [ 1, 91, 92, 39, 227, 205, 68, 235, 66, 61, 195, 247, 217, 47, 30, 125, 113, 20, 209, 248, 181, 121, 230, 158, 63, 157, 160, 202, 27, 152, 159, 202, 26, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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